Syncing Microsoft Entra ID (Azure AD) with Google Workspace Using Directory Sync
Syncing Microsoft Entra ID with Google Workspace via Directory Sync eliminates on-premises software, automates user and group provisioning, reduces manual administrative workload, prevents stale accounts during offboarding, maintains consistent directory records across platforms, and enhances security by centralizing cloud identity lifecycle management.
What is Directory Sync?
Directory Sync synchronizes user and group data from an external directory to your Google cloud directory. It runs in the cloud, so there is no sync client or on-premises software to install. It supports both Microsoft Active Directory and Microsoft Entra ID. Currently Google labels the feature as public beta, so to check its current status before a production rollout.
Purpose to Connect Entra ID as an External Directory
- A single source of truth. Admins manage identities in the system they already use, and Google Workspace follows. For example, when HR marks someone as terminated in Entra ID, that change carries over without a second manual step.
- Less repetitive work. New hires appear in Google Workspace without a separate account-creation process.
- Consistent access. Group memberships stay aligned across platforms. If “Finance-Team” is a group in Entra ID, the same group and its members can exist in Google Workspace and control access to shared drives.
- Fewer errors. Automation removes typos, forgotten deprovisioning, and orphaned accounts.
Prerequisites
- The custom DNS domains to be synced must be added and verified in both Google Cloud and Entra ID platforms
- Allow pop-ups in your browser, to initiate the authorization by granting the Google Workspace Directory Sync Application the necessary Microsoft Graph API access to read directory data.
- Use a Google Super admin account with the Manage Directory Sync Settings privilege.
- On the Microsoft side, you will require an account preferably with Global Administrator privileges allowing read access so that full profiles, groups, and memberships can be read.
Steps to add Entra ID as an External Directory
Ensure an account is available within the Entra ID with at least Global Administrator or Cloud Application Administrator privileges. The domains we intend to sync (e.g., abc.com) are required to be configured as primary or secondary custom domains in both Entra ID and Google Workspace.
Open the Microsoft Entra Admin Center. Go to Groups and create a security Group with members included in it to sync to Google Workspace Directory. Groups must have their own associated email address in the external directory.
Keep members added to the Group to later sync to Google Workspace.
Log into the Google Admin Console as a Super Admin, navigate to Directory > External directories, click Add Azure Active Directory, give it a name, and hit Authorize and Save.
Sign in to Microsoft with your Entra Global Admin account. On the permissions prompt, check Consent on behalf of your organization and click Accept. This automatically sets up the Google Directory Sync app in your Entra tenant.
Once the Connection is successful, Click Continue.
In case connection failure occurs, recheck the prerequisites and ensure the same is followed along with reviewing the reason for failure and troubleshooting the failed connection.
You will find the created custom External Directory within Directory Sync. Go to User Sync.
Now enter the external directory group name, ie, the security group created within Entra ID to sync the group members to your Google cloud directory. The group name is case sensitive and needs to be entered correctly.
Start Verification to validate the group by pressing Continue.
One may choose to keep the users mapped to a single Organization Unit in Google or else enter the user attribute available with the Entra ID containing the full path to the organizational unit.
Additionally to keep the users synced to the respected paths within the individual directories, one may choose to enforce the policy to restrict movement of users to a separate OU or allowing the same.
Now collect the user attributes as per Microsoft valid Graph Properties. As the attributes are case sensitive, please note Graph’s JSON uses camelCase keys. In case you click on Set default, it updates the required properties automatically.
To add any custom attributes, one can refer to the following URL<learn.microsoft.com/graph/api/resources/user> to find the user properties with the JSON representation under the Microsoft Graph group resource type.
One may decide to send the account activation mail directly to the user's primary or recovery email address or not to send an email, when using a third-party identity provider (IdP) for authentication.
Google automatically runs a full sync interval starting 1 hour after the previous sync finishes by pulling the data from external directories. Here directory sync using Entra ID is restricted to only one directory within the Google Workspace account.
If the group is removed from the external directory or the user accounts are removed from the group, one can enable the option to suspend users within Google Directory. Now if the user is forcefully suspended in Google directory where the account is active within the external directory under the group, the user's account is activated following a sync.
Necessary safeguards can be applied to prevent users getting suspended in Google on the basis of percentage of users or number of users.
To verify the sync completion status, go to View Simulation Logs to find the Directory Sync Logs Events to find the Sync Status and objects (user account) creation status.
In case the sync is encountering failure, ensure the sync status is Active.
Similar to the User account synchronization, one can choose to synchronize existing M365 groups, distribution list or mail enabled security groups, provided they have group mail addresses with the domain already added in Google.
The default .onmicrosoft.com domain cannot be registered or synced to Google Cloud.
Once done, click Verify to check if the groups added in Microsoft Entra ID and click on Continue.
Next, verify whether the preselected attributes match the default user properties contained within the user resource under external directory. Once done click Continue.
The synced Google Group can be auto removed by enabling the condition where the group is either deleted to disabled under the external directory. Once checked, Click Continue.
To safeguard the groups from getting auto deleted during the sync attempts, conditions can be set on the basis of percentage of groups or total number of groups.
Conclusion
Adding Entra ID as an external directory means one identity system drives both platforms. The setup takes only a few steps in the Admin console, and the one-way, read-only design keeps your Microsoft environment safe. It is necessary to plan your groups first and always run a simulated sync before the real one to maintain data consistency.