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 DeploymentFlow.md #463

Merged
merged 3 commits into from
Feb 24, 2023
Merged

Update DeploymentFlow.md #463

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
84326db
Update DeploymentFlow.md
baartch Feb 24, 2023
9598c83
Update docs/wiki/DeploymentFlow.md
jtracey93 Feb 24, 2023
4e34890
Update docs/wiki/DeploymentFlow.md
jtracey93 Feb 24, 2023
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
6 changes: 3 additions & 3 deletions docs/wiki/DeploymentFlow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,9 @@ The current available orchestration modules are listed below:

## Deployment Identity

> When first working with Management Groups, the Azure AD Global Administrator must assign the User Access Administrator role to themselves at the `/` scope first before being able to further delegate. See [Elevate access to manage all Azure subscriptions and management groups](https://learn.microsoft.com/azure/role-based-access-control/elevate-access-global-admin) documentation for further information.
When first working with Management Groups, the Azure AD Global Administrator must assign the User Access Administrator role to themselves at the `/` scope first before being able to further delegate. See [Elevate access to manage all Azure subscriptions and management groups](https://learn.microsoft.com/azure/role-based-access-control/elevate-access-global-admin) documentation for further information.

In addition, the identity that wants to create a Tenant scope deployment must have the _Owner_ role assigned to the `/` root management group. Whether this is your user account (even if a Global Administrator) or a Service Principal. See [Required access for Tenant deployments on Azure Docs](https://learn.microsoft.com/azure/azure-resource-manager/templates/deploy-to-tenant?tabs=azure-powershell#required-access).
jtracey93 marked this conversation as resolved.
Show resolved Hide resolved

### Service Principal Account

Expand All @@ -93,8 +95,6 @@ A service principal account is required to automate through Azure DevOps or GitH
- Scope: `/` (Root Management Group)
- Role Assignment: `Owner`

> See [step-by-step instructions on Azure Docs](https://learn.microsoft.com/azure/azure-resource-manager/templates/deploy-to-tenant?tabs=azure-powershell#required-access) to configure the role assignment at `/` root management group.

### Configure Service Principal Account in Azure DevOps or GitHub

- Azure DevOps: [Setup Service Connection](https://learn.microsoft.com/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml)
Expand Down