RM Logo
Technical Rating: 
Support Home PageSupport
Print This PagePrint This Page
Add to 'My Library' Add to 'My Library'

Unable to match existing Google Workspace accounts to RM Unify when Microsoft 365 is already installed
Published Date : 09 Dec 2015   Last Updated : 04 Oct 2024   Content Ref: TEC4904117  





Symptoms

You have Microsoft® 365™ federated to RM Unify and wish to also connect your Google Workspace domain. When you complete the Google Workspace connector wizard to install the app to your Launch Pad you see the following error message:

"Sorry, RM Unify doesn't support editing the Google Workspace email addresses assigned to your RM Unify users when the Microsoft 365 connector is also installed".

A similar issue and error will also occur if you have Google Workspace installed to RM Unify already and you wish to federate Microsoft 365 and brownfield match your RM Unify users to existing Microsoft 365 accounts.



Procedure

RM Unify will provision your Google Workspace accounts using the userid part of the RM Unify email address, plus the Google Workspace domain.

Here are some examples of outcomes:

RM Unify username Microsoft 365 federated domain RM Unify Email Address Desired Google Workspace federated domain Email address RM Unify will send to Google Workspace after federation
joe.smith@school SchoolA.com joe.smith@SchoolA.com SchoolA.com joe.smith@SchoolA.com
joe.smith@school SchoolA.com jsmith@SchoolA.com SchoolA.com jsmith@SchoolA.com
joe.smith@school SchoolA.com joe.smith@SchoolA.com SchoolTrust.com joe.smith@SchoolTrust.com
joe.smith@school SchoolA.com jsmith@SchoolA.com SchoolTrust.com jsmith@SchoolTrust.com

It is not possible to brownfield match to existing Google Workspace users where the Google account name does not match the email address RM Unify will send. You can, however, change the existing Google account names so that they do match what RM Unify will send prior to federation. In this way you will be able to match your RM Unify users to their existing Google Workspace account.

Please refer to TEC4945314 in the Other Useful Articles section below.



Possible Issues

If you had Microsoft 365 or Google Workspace federated to RM Unify in the past, but not currently, the caching of those previous domain's configuration settings will also prevent you from using brownfield user matching. RM cache the previous configuration to make refederation of the domain quick and simple, however, in some circumstances it can become an issue. The issue will be resolved in a future release of RM Unify, but for now please log a call with RM Support to get the old settings cleared from the database.



Other Useful Articles

Supported configurations when federating your RM Unify establishment(s) to Microsoft 365 and/or Google Workspace (TEC4945314)

FEEDBACK
Did the information in this article help answer your question?
 Yes
 No
Please add any comments about this article in the box below. If you answered No then it is important you tell us why so that we can change the article if required. We can only respond if you log in to the RM Support website or provide your contact details. Note: If you need help with a technical query, please log a call online or telephone our support team.
Thank you for your feedback, which is sent directly to the RM Knowledge team. We address every message received with the intention of improving our Knowledge Library articles. If you have an unresolved technical issue, please contact RM Support.


If this article has not helped provide a solution then it is also possible to log a call...



Document Keywords: unify, google, apps, google app o365, GAfE, Google Apps, Google Apps for Education, dual federation, joint, unable to match existing accounts, o365 wizard, Sorry, RM Unify doesn't support editing the Google Workspace email addresses assigned to your RM Unify users when the Office 365 connector is also installed, Google Workspace, g suite, TEC4904117


Please read - important disclaimer information.
http://www.rm.com/_RMVirtual/Includes/csredirect.asp?cref=&title=Standard Content Disclaimer


Top Of PageTop of page