Stay organized with collections Save and categorize content based on your preferences.
Last reviewed 2024-06-26 UTC
The documents in the Assess and plan section help you assess your requirements and develop a plan for onboarding your corporate identities to Cloud Identity or Google Workspace.
Managing corporate identities is often one of the key responsibilities of enterprise IT departments. But each organization is unique, and the way you manage corporate identities in your organization is likely to be unique, too. To determine the best way to use Cloud Identity or Google Workspace to manage corporate identities in your organization, it's important that you assess your requirements.
Before you beginBefore you begin to assess and plan your Cloud Identity or Google Workspace deployment, make sure that you do the following:
To assess and plan your Cloud Identity or Google Workspace deployment, follow these steps:
If you selected an architecture that uses an external IdP, learn how to map the logical model of your external IdP to Cloud Identity or Google Workspace.
If you use Active Directory, refer to Federating with Active Directory to learn how to map forests, domains, users, and groups and learn which configuration options to consider.
Similarly, if you plan to federate with Azure Active Directory (AD), see Federating with Azure AD for more details on how you can map tenants, domains, users, and groups.
Identify and assess existing user accounts. If you haven't been using Google Workspace or Cloud Identity, it's possible that your organization's employees have been using consumer accounts to access Google services. Before you set up Google Workspace or Cloud Identity, we recommend that you analyze user accounts that exist and how to best deal with them.
For more details on the different sets of user accounts you might have and how they can impact your deployment, see Assess existing user accounts.
Settle on a high-level plan for onboarding identities to Cloud Identity or Google Workspace. In Assess onboarding plans, you can find a selection of proven onboarding plans, along with guidance on how to select the plan that best suits your needs.
If you plan to use an external IdP and have identified user accounts that need to be migrated, you might need to consider additional requirements when configuring your external IdP. For more details, see Assess user account consolidation impact on federation.
When you have completed your assessment and created a plan, you will be ready to onboard your corporate identities to Cloud Identity or Google Workspace.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-06-26 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-06-26 UTC."],[[["This section focuses on assessing requirements and planning the onboarding of corporate identities to Cloud Identity or Google Workspace."],["Before starting, it is recommended to understand the domain model, determine the need for single or multiple Google Cloud organizations, and review relevant reference architectures."],["The assessment process involves mapping external Identity Provider (IdP) logical models, such as Active Directory or Azure AD, to Cloud Identity or Google Workspace."],["It's crucial to identify and analyze existing user accounts, especially if employees have been using consumer accounts, and determine how they will affect your deployment."],["A high-level plan for onboarding identities should be established, utilizing proven onboarding plans and considering the impact of external IdP usage and potential user account migrations."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4