"Microsoft 365 access ended" and "GDAP access ends" warnings
What to do when a client's GDAP relationship has ended, or ends within 30 days and won't renew on its own.
Written By The Lemhi Product Team
Last updated 10 days ago
This is for the MSP admin who sees a client's GDAP relationship ending or already ended. Both are about the relationship in your Partner Center, not about Partner Connect. Reconnecting Partner Connect fixes neither.
Microsoft 365 access ended on <date>
The client's admin relationship with your Partner Center ended. The client list and the client's settings show Access ended. The client's overview shows this heading with: "The client's admin relationship with your Partner Center ended. When the client approves a new relationship, Lemhi reconnects automatically." When Lemhi doesn't know the end date, the heading reads "Microsoft 365 access ended".
In Partner Center, request a new relationship with the six roles. See Step 1.
Send the client the approval link. Their admin approves it as in Step 2.
Assign your security group to the new relationship. See Step 3.
Once the client approves, Lemhi reconnects the client automatically.
GDAP access ends <date>
The client is connected, but its relationship ends within the next 30 days and won't renew on its own. Lemhi shows this only when auto-extend is off for that relationship. It appears in the client list, on the client's overview and in its settings.
In Settings > Microsoft Partner Account > Review connection, the client's row under Client connections shows GDAP relationship ending soon with:
"<client>'s GDAP relationship "<relationship name>" ends on <date> and won't renew automatically."
In Partner Center, turn on auto-extend for the relationship, or request a new one before the date.
The finding has an Open Partner Center button. If you request a new relationship, follow Step 1 through Step 3 before the date so the client doesn't lapse.
Auto-extend renews a relationship six months at a time. Microsoft won't auto-extend a relationship that includes Global Administrator, so Lemhi's role list leaves it out.
Related
Still stuck? Send your Lemhi contact the client name, the date Lemhi shows, and the relationship name from Partner Center.
Was this helpful?
More in Troubleshooting
Partner Connect stopped working: what the banner says and how to fix itClient won't connect: "Microsoft declined this connection" and other import errorsDisconnect a client or revoke Lemhi's accessStill need help? Ask the team