Why isn't EwsAllowedAppIDs available in my Exchange Online session?

November 14, 2026 3 answers
Asked by 8m!thimblecase_273

I'm trying to enable EWS temporarily and restrict it to selected Entra application IDs. The documented Set-OrganizationConfig command fails because EwsAllowedAppIDs isn't recognized, even after updating ExchangeOnlineManagement.

Could this be a tenant rollout issue, or is there something else I should check?

Answers

a39~screwcap_814

A missing parameter can mean the command exposed in your current session doesn't include it yet. Check the parameters on Set-OrganizationConfig in the connected Exchange Online session, not just the installed module version. A rollout delay is possible, but that error alone doesn't establish the cause or tell you when your tenant will get it.

If it still isn't listed after reconnecting with the current module, ask Microsoft support whether the feature is available for your tenant. The source discussion doesn't give a confirmed tenant-specific rollout date.

Reply to this answer
h37+ticketfold_829

I'd also check which administrative roles are active in the session and whether EwsEnabled has to be set separately first. Those are troubleshooting ideas, not confirmed prerequisites for this parameter.

Since the module was already updated, repeating that step alone probably won't narrow it down much.

Reply to this answer
q.82+turnabout

Keep the EWS retirement timeline separate from this parameter problem. A reported plan to auto-populate the allowed app IDs in September suggests a possible rollout milestone, but it isn't a confirmed date for any particular tenant. Check Microsoft's current retirement and rollout guidance before scheduling the change.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions