Exchange Admin - Migration Endpoints are Missing / not showing

Bantha 0 Reputation points
2026-09-04T07:43:37.52+00:00

Hello Guys,

were running Hybrid Exchange Environment.

Since last Week im no longer able to load our Migration Endpoints.

https://admin.cloud.microsoft/exchange#/migrationbatch

I got the Role "Exchange Admin" and cant see the Endpoints.

My colleagues got the Role "Global Admin" and can see the Endpoints.

Chrome Console shows following Error:
GET https://exchange.admin.cloud.microsoft/beta/MigrationEndpoint 500 (Internal Server Error)

Remove and Re-Assign the Exchange Admin role doesnt solve the Problem.
In-Private / Incognito Browser doesnt solve the Problem.
Complete new Notebook/PC (never logged in before) doesnt solve the Problem.

What else can i try?

Exchange | Hybrid management
Exchange | Hybrid management

The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Bantha 0 Reputation points
    2026-09-04T11:09:16.6533333+00:00

    New User, same Problem.

    I will open an Support Case.

    Thanks for your help.

    Was this answer helpful?

    0 comments
  2. Hani-Ng 965 Reputation points Independent Advisor
    2026-09-04T09:46:03.3166667+00:00

    Hi Bantha

    Since the behavior follows your account across multiple browsers and devices, while other admins can view the Migration Endpoints without issue, this doesn't appear to be a client-side problem.

    Based on the information provided, the problem seems to occur only when Migration Endpoint data is being accesse. Get-MigrationEndpointreturns an exception, while Get-MigrationConfig Get-MigrationBatchreturn results successfully. The Exchange admin center is also showing an HTTP 500 error when requesting MigrationEndpoint data.

    The exception you're getting (Microsoft.Incubation.Crypto.GroupKeys.ADRepository) is also not a typical permissions error. Normally, a missing permission would return an access denied message rather than a backend exception. The HTTP 500 error from the Exchange admin center points in the same direction.

    As an additional test, I'd suggest checking whether a completely new account with only the Exchange Administrator role can reproduce the issue. If the new account works, that would indicate something specific to the affected admin account rather than the tenant itself.

    If the problem continues, I would recommend opening a Microsoft support ticket and providing the RequestId from the PowerShell error. Since both EAC and PowerShell encounter the same issue when accessing Migration Endpoints, Microsoft support team should be able to trace the request and investigate the backend service response.

    You can follow this guide to open support ticket: Get support - Microsoft 365 admin | Microsoft Learn.   

    I hope this information helps.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.