This article applies to organizations that migrated from EWS to Exchange Online Admin API before November 17, 2026. If your organization migrated on or after that date, your IT administrator already consented to Exchange.AdminAPI.Manage during setup and no further action is required.
Microsoft is replacing the Exchange Online Admin API permission that ContactMonkey uses to expand your distribution lists. Your IT administrator must approve the new permission before November 30, 2026 to keep distribution list expansion working.
Important: The Microsoft Graph integration migrated to a new permission separately. If your organization uses that expansion method, follow the steps in Migrating to the GroupMember.Read.All Permission for Microsoft Graph to complete that update.
What is changing with the Exchange Online Admin API permission?
Microsoft is retiring Exchange.ManageV2 and replacing it with Exchange.AdminAPI.Manage. Microsoft announced this on November 5, 2026.
The Exchange Online Admin API itself is not changing. Endpoint URLs, API version, and supported operations all stay the same. Only the permission changes.
| Date | What happens |
|---|---|
| November 1, 2026 | The new permission becomes available. |
| November 30, 2026 | Deadline to grant consent to the new permission. |
| December 1, 2026 |
Exchange.ManageV2 stops working. |
ContactMonkey has already updated and tested its side of the integration. Admin consent is the only step remaining.
Do I need to take action?
ContactMonkey Admins must navigate to Settings → Integrations and check which tiles are signed in.
- Exchange Admin Utility Account is signed in: yes, complete the steps below.
- Only Graph Utility Account is signed in: no action is required for this change.
- Neither is signed in: no action is required. Your organization does not use Exchange Online Admin API expansion.
What happens if no action is taken?
On December 1, 2026, your Exchange Online Admin (EOA) connection stops working. ContactMonkey can no longer expand your distribution lists through it, so emails sent to those lists may not reach everyone they should.
1. Grant the new permission (IT Admin)
| API Resource | Permission Type | Scope |
|---|---|---|
| Office 365 Exchange Online | Delegated | Exchange.AdminAPI.Manage |
ContactMonkey has already added the new permission to the ContactMonkey - Exchange Online Admin API enterprise app. Grant consent using the Admin Consent URL for the region your ContactMonkey data is stored in. These are the same links used for the original Exchange Online Admin API migration, so running one again approves the new permission.
You must be signed in as a Global Administrator or Privileged Role Administrator to approve the permission. You will be redirected to a login screen — you are not required to enter your credentials if you do not have a ContactMonkey account.
Once consent is granted, your EOA connection picks up the new permission automatically. Nobody needs to reconnect or sign in again.
2. Confirm the RBAC role is still assigned (IT Admin)
Microsoft's existing Exchange role requirements still apply. Confirm that the service account connected to ContactMonkey still holds the View-Only Organization Management role in the Exchange Admin Center.
- Open the Exchange Admin Center
- Navigate to Roles → Admin roles
- Search for and select View-Only Organization Management
- Click the Assigned tab, search for and add your Service Account

3. Verify the connection (ContactMonkey Admin)
- Click your name at the top right of the ContactMonkey dashboard
- Click Settings
- Click Integrations
- Click Show Details in the Exchange Admin Utility Account tile
- In the Distribution List field, enter one or more distribution list email addresses (comma-separated)
- Click Test Count
- Results will be emailed to you
If the recipient count matches your expected number, the new permission is working.
Troubleshooting
Problem: The consent link shows "Need admin approval" or returns an error.
Solution: The signed-in account is not a Global Administrator or Privileged Role Administrator. Forward the link to someone who holds one of those roles.
Problem: The recipient count does not match expectations.
Solution: See Troubleshooting Distribution List Expansion for diagnostic steps.
Problem: The Exchange Admin Utility Account tile shows "Inactive".
Solution: This usually means OAuth tokens have expired. Running a Test Count should reactivate the account. If it remains inactive, sign out and sign back in.
Problem: You are not sure whether consent was already granted.
Solution: See How to Confirm Your Microsoft Graph and Exchange Online Admin API Migration Is Complete.