Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update tenant.md #407

Merged
merged 1 commit into from
Feb 26, 2018
+2 −2
Merged

Update tenant.md #407

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/cloud-adoption-guide/adoption-intro/tenant.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ An Azure AD tenant provides digital identity services and namespaces used for on
## Design considerations

- At the foundational adoption stage, you can begin with a single Azure AD tenant. If your organization has an existing Office 365 subscription or an Azure subscription, you already have an Azure AD tenant that you can use. If you do not have either or of these, you can learn more about [how to get an Azure AD tenant][how-to-get-aad-tenant].
- In the intermediate and advanced adoption stages, you will learn how to synchronize or federate on-premises directories with Azure AD. This will allow you to use on-premises digital identity in Azure AD. However, at the foundational stage, you will be adding new users that only have identity your single Azure AD tenant. You are be responsible for managing those identities. For example, you will have to on-board new Azure AD users, off-board Azure AD users that you no longer wish to have access to Azure resources, and other changes to user permissions.
- In the intermediate and advanced adoption stages, you will learn how to synchronize or federate on-premises directories with Azure AD. This will allow you to use on-premises digital identity in Azure AD. However, at the foundational stage, you will be adding new users that only have identity your single Azure AD tenant. You will be responsible for managing those identities. For example, you will have to on-board new Azure AD users, off-board Azure AD users that you no longer wish to have access to Azure resources, and other changes to user permissions.

## Next Steps

Expand All @@ -23,4 +23,4 @@ An Azure AD tenant provides digital identity services and namespaces used for on
[docs-manage-azure-ad]: /azure/active-directory/active-directory-administer?toc=/azure/architecture/cloud-adoption-guide/toc.json
[docs-tenant]: /azure/active-directory/develop/active-directory-howto-tenant?toc=/azure/architecture/cloud-adoption-guide/toc.json
[docs-associate-subscription]: /azure/active-directory/active-directory-how-subscriptions-associated-directory?toc=/azure/architecture/cloud-adoption-guide/toc.json
[how-to-get-aad-tenant]: /azure/active-directory/develop/active-directory-howto-tenant?toc=/azure/architecture/cloud-adoption-guide/toc.json
[how-to-get-aad-tenant]: /azure/active-directory/develop/active-directory-howto-tenant?toc=/azure/architecture/cloud-adoption-guide/toc.json