It is similar to objectGUID in Active Directory. Office 365 has an immutableId attribute to uniquely identify users (primaryKey). Users should be automatically provisioned (and de-provisioned) in Office 365 when they are provisioned (and de-provisioned) in Google Workspace or Google Cloud Identity.If our users directly go to Office 365, they should be redirected to their Google Cloud Identity (or Google Workspace) login page, and then back to Office 365 after success Google login.Our users should see the Office 365 application icon in their Google Workspace or Cloud Identity dashboard and launcher, and when they click on it, they should be logged into Office 365 (via their Google Identity) without being asked for credentials.Let’s start with our expected output, we should see following after our setup-: In this blog post, I would show you how you can use Google Cloud Identity or Google Workspace as identity provider and use Google Workspace SSO to sign in Office 365 via SAML 2.0 (or WS-Fed). Google Cloud Identity is very flexible and it can be used as “Service Provider”, Identity provider or even both. Your organization has moved to Google Cloud Identity as your Identity provider and now needs to authenticate to target applications including Office 365.Your organization has moved to Google Workspace, but a few users still have accounts in Office 365.So your Office 365 users can authenticate via their Google Workspace or Google Cloud Identity accounts.Ī couple of use cases that I have seen are-: There might be use cases where you would like to setup Google Workspace SSO to office 365.
0 kommentar(er)
