[GH-ISSUE #178] Tenant Access Check Exchange Error #105

New issue

Closed

opened 2026-03-02 12:03:55 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 12:03:55 +03:00

Owner

Originally created by @mr-macedawg on GitHub (Nov 3, 2021).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/178

Describe the bug
When running the Tenant Access Checker the following error appears when testing Exchange.

Failed to connect to Exchange: AADSTS9002313: Invalid request. Request is malformed or invalid. Trace ID: f8eaa7cf-6e0a-48bb-9916-12bc4af21600 Correlation ID: b11ebb73-2ada-4d1a-902e-953712ae2355 Timestamp: 2021-11-03 11:04:56Z

To Reproduce
Steps to reproduce the behavior:

Go to Configuration Settings
Select a Tenant under Tenant Access Checker
Click Run access check
See error

Desktop (please complete the following information):

OS: Windows 11
Browser: Google Chrome
Version: 95.0.4638.69

Additional context
CIPP Version 1.2.1
CIPP API Version 1.2.3

Originally created by @mr-macedawg on GitHub (Nov 3, 2021). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/178 **Describe the bug** When running the Tenant Access Checker the following error appears when testing Exchange. > Failed to connect to Exchange: AADSTS9002313: Invalid request. Request is malformed or invalid. Trace ID: f8eaa7cf-6e0a-48bb-9916-12bc4af21600 Correlation ID: b11ebb73-2ada-4d1a-902e-953712ae2355 Timestamp: 2021-11-03 11:04:56Z **To Reproduce** Steps to reproduce the behavior: 1. Go to Configuration Settings 2. Select a Tenant under Tenant Access Checker 3. Click Run access check 4. See error **Desktop (please complete the following information):** - OS: Windows 11 - Browser: Google Chrome - Version: 95.0.4638.69 **Additional context** CIPP Version 1.2.1 CIPP API Version 1.2.3

kerem

2026-03-02 12:03:55 +03:00

closed this issue
added the
NotABug
label

kerem commented

2026-03-02 12:03:56 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Nov 3, 2021):

Not a bug, you either entered an incorrect ExchangeRefreshToken, or left it empty.

@KelvinTegelaar commented on GitHub (Nov 3, 2021): Not a bug, you either entered an incorrect ExchangeRefreshToken, or left it empty.

kerem referenced this issue

2026-03-02 13:54:59 +03:00

[PR #105] [MERGED] Updating dev #2683

kerem referenced this issue

2026-03-02 13:55:03 +03:00

[PR #136] [MERGED] Upgrading Dev to Release #2695

kerem referenced this issue

2026-03-02 13:58:25 +03:00

[PR #1869] [MERGED] Mailbox Restore Actions #3459