Microsoft Entra ID
Provisioning

Configure Google Cloud / Google Workspace for automatic user provisioning with Microsoft Entra ID

In brief

The documentation now states that manually ending an active PIM group membership before its scheduled expiry does not trigger accelerated deprovisioning. Removal may occur during the next provisioning synchronization, which can take up to about 40 minutes.

What Entra admins need to know

Plan for up to about 40 minutes before manually ended memberships are removed.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

title: Configure Google Cloud / Google Workspace for automatic user provisioning with Microsoft Entra ID description: Learn how to automatically provision and deprovision user accounts from Microsoft Entra ID to Google Cloud or Google Workspace. ms.topic: how-to ms.date: 10/30/11/16/2026 ms.custom: sfi-image-nochange, msecd-doc-authoring-1032 ai-usage: ai-assisted

Customer intent: As an IT administrator, I want to learn how to automatically provision and deprovision user accounts from Microsoft Entra ID to Google Cloud / G Suite Connector by Microsoft so that I can streamline the user management process and ensure that users have the appropriate access to Google Cloud / G Suite Connector by Microsoft.

  1. Use on-demand provisioning to create the group in Google Cloud / Google Workspace.
  2. Sign-in to Google Cloud / Google Workspace and assign the second group the necessary permissions to perform admin tasks.

Now any end user that was made eligible for the group in PIM can get JIT access to the group in Google Cloud / Google Workspace by activating their group membership. When their assignment expires,reaches its scheduled expiry, the user is removed from the group in Google Cloud / Google Workspace. During the next incremental cycle, the provisioning service attempts to remove the user from the group again. This might result in an error in the provisioning logs. This error is expected because the group membership was already removed. The error message can be ignored.

  • How long does it take to have a user provisioned to the application?
    • The group membership is provisioned in 2 – 10 minutes. When there's a high rate of requests at one time, requests are throttled at a rate of five requests per 10 seconds.
    • For the first five users within a 10-second period activating their group membership for a specific application, group membership is provisioned in the application within 2-10 minutes.
    • For the sixth user and beyond within a 10-second period activating their group membership for a specific application, group membership is provisioned to the application in the next synchronization cycle. The synchronization cycle runs every 40 minutes. The throttling limits are per enterprise application.
  • If a user manually ends an active PIM group membership before its scheduled expiry, accelerated deprovisioning isn't triggered. The membership removal can be processed during the next regular provisioning synchronization cycle, which can take up to about 40 minutes. This early-termination delay doesn't apply when the activation reaches its scheduled expiry.
  • If the user is unable to access the necessary group in Google Cloud / Google Workspace, review the PIM logs, and provisioning logs to ensure that the group membership was updated successfully. Depending on how the target application is architected, it might take more time for the group membership to take effect in the application.
  • You can create alerts for failures using Azure Monitor.
Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…