As we prepare for the final phase of Exchange Web Services retirement, we are refining how EWSAllowedAppIDs setting (which you can use to define your EWS AppID allow list) will be applied. Our goal i...
Published Sep 04, 2026
Version 1.0
Blog Post
Nino_Bilic
Microsoft
MicrosoftNo, this should be available to all tenants. I do have a few suggestions for you to check, though:
- Check that the account that you are using has the RBAC rights; see "Test a user's Exchange Online RBAC permissions" diagnostic here: Self-help diagnostics for issues in Exchange Online and Outlook - Exchange | Microsoft Learn
- If that checks out, run the "Exchange Organization Object check" diagnostic on the same page. It is possible (but unlikely) that there is something up with the tenant that should get sorted out and this diagnostic might help
If still no go, please DM me the tenant ID.
Thanks Nico good suggestion with the RBAC test which confirms it's not available in our tenant. I DM you the tenant ID.
Run Tests: EXO RBAC test user
These are the key insights regarding the user RBAC permissions diagnostic results.
- Couldn't find a management role allowing access to cmdlet 'set-OrganizationConfig' with the parameter 'EwsAllowedAppIDs'. The parameter appears to be mistyped.
There is a known issue affecting quite a few tenants where the EwsAllowedAppIDs parameter is unavailable.
No advisory has been published, yet the EWS deadline is this week.
We are essentially being asked to drive the car while Microsoft is still installing the steering wheel.... I'm waiting for the car crash 😨
- Greg Taylor - EXCHANGE
There is no 'known issue' Joshua Bines​ - in every case this has come up the user does not have the RBAC role required - Use someone with the Exchange Admin role assigned. I assume you are trying to add the cmdlet to some custom role you have created?
Well, that's a worry because support is telling me the opposite, and they're seeing more of these tickets coming in. The RBAC Diagnostic test can't find the parameter 'EwsAllowedAppIDs' that can't be expected right? I'll DM you the Case number.
There are no custom roles involved. The account has the Exchange Administrator role, and I even added it to the Organization Management role group just to rule out any RBAC issues. I'm using PowerShell 7.6.6 with Exchange Online Management Module 3.10.1. I tested access to other tenants without issues.
I also ran the EXO RBAC Test User Diagnostic, which returned the following result:
"Couldn't find a management role allowing access to cmdlet 'Set-OrganizationConfig' with the parameter 'EwsAllowedAppIDs'. The parameter appears to be mistyped."
