[GH-ISSUE #1421] 'LastGraphError' cannot be found on this object #788

Closed
opened 2026-03-02 12:45:13 +03:00 by kerem · 5 comments
Owner

Originally created by @twilson-gl on GitHub (Mar 18, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1421

Description

Under Settings > CIPP > Settings > Tenant Access Check

Running an access check on any tenant results in the following message:

Failed to connect to The property 'LastGraphError' cannot be found on this object. Verify that the property exists and can be set.
Failed to connect to Exchange: The property 'LastGraphError' cannot be found on this object. Verify that the property exists and can be set.

image

Not quite sure what this is referencing or where to look to resolve it.

Environment data

Azure - Frontend/Backend Version: 3.2.0
Originally created by @twilson-gl on GitHub (Mar 18, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1421 ### Description Under Settings > CIPP > Settings > Tenant Access Check Running an access check on any tenant results in the following message: _Failed to connect to The property 'LastGraphError' cannot be found on this object. Verify that the property exists and can be set._ _Failed to connect to Exchange: The property 'LastGraphError' cannot be found on this object. Verify that the property exists and can be set._ ![image](https://user-images.githubusercontent.com/61714585/226074194-13bb4f98-0ab9-427d-8d72-97b63f94b334.png) Not quite sure what this is referencing or where to look to resolve it. ### Environment data ```PowerShell Azure - Frontend/Backend Version: 3.2.0 ```
kerem 2026-03-02 12:45:13 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Mar 18, 2023):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

<!-- gh-comment-id:1474550951 --> @github-actions[bot] commented on GitHub (Mar 18, 2023): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.". Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
Author
Owner

@twilson-gl commented on GitHub (Mar 18, 2023):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

<!-- gh-comment-id:1474551006 --> @twilson-gl commented on GitHub (Mar 18, 2023): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
Author
Owner

@KelvinTegelaar commented on GitHub (Mar 18, 2023):

I'm thinking this might be a bug we introduced with the new tenant overview. Can you try removing your tenant cache and seeing if that helps?

<!-- gh-comment-id:1474554286 --> @KelvinTegelaar commented on GitHub (Mar 18, 2023): I'm thinking this might be a bug we introduced with the new tenant overview. Can you try removing your tenant cache and seeing if that helps?
Author
Owner

@twilson-gl commented on GitHub (Mar 18, 2023):

Noiiice! That did it.

Thanks Kelvin :)

<!-- gh-comment-id:1474555024 --> @twilson-gl commented on GitHub (Mar 18, 2023): Noiiice! That did it. Thanks Kelvin :)
Author
Owner

@KelvinTegelaar commented on GitHub (Mar 18, 2023):

awesome! no problem :)

<!-- gh-comment-id:1474555080 --> @KelvinTegelaar commented on GitHub (Mar 18, 2023): awesome! no problem :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#788
No description provided.