Enterprise-Scale/docs/wiki/Deploying-ALZ-Pre-requisite...

63 строки
3.0 KiB
Markdown
Исходник Постоянная ссылка Ответственный История

Этот файл содержит неоднозначные символы Юникода!

Этот файл содержит неоднозначные символы Юникода, которые могут быть перепутаны с другими в текущей локали. Если это намеренно, можете спокойно проигнорировать это предупреждение. Используйте кнопку Экранировать, чтобы подсветить эти символы.

## Enterprise-Scale Prerequisites
Enterprise-Scale can bootstrap an entire Azure tenant without any infrastructure dependencies, and the user must first have Owner permission on the tenant *root* before deploying.
*Note: Once you have completed the deployment, you can remove the Owner permission from the tenant root, as it will no longer be needed for any subsequent operations.*
This requires the following:
* A user that is Global Admin in the Microsoft Entra ID
* Elevation of privileges of this user which grants him/her the “User Access Administrator” permission at the tenant root scope
* An explicit roleAssignment (RBAC) made at the tenant root scope via CLI or PowerShell (Note: Theres no portal UX to make this roleAssignment)
### Elevate Access to manage Azure resources in the directory
1.1 Sign into the Azure portal as a user being Global Administrator
1.2 Open Microsoft Entra ID
1.3 Under *Manage*, select *Properties
![Graphical user interface, text, application, Teams Description automatically generated](./media/clip_image006.jpg)
1.4 Under *Access management for Azure resources,* set the toggle to *Yes
![Graphical user interface, text, application, email Description automatically generated](./media/clip_image008.jpg)
### Grant Access to the User at *tenant root scope “/”* to deploy Enterprise-Scale
You can use either Bash (CLI) or PowerShell to create the roleAssignment for the current user – or a dedicated user – that will do the deployment.
Bash:
```bash
#sign into AZ CLI, this will redirect you to a web browser for authentication, if required
az login
#assign Owner role to Tenant root scope ("/") as a Owner (gets object Id of the current user (az login))
az role assignment create --scope '/' --role 'Owner' --assignee-object-id $(az ad signed-in-user show --query id --output tsv)
```
Powershell:
```powershell
#sign in to Azure from Powershell, this will redirect you to a web browser for authentication, if required
Connect-AzAccount
#get object Id of the current user (that is used above)
$user = Get-AzAduser -SignedIn
#assign Owner role to Tenant root scope ("/") as a User Access Administrator
New-AzRoleAssignment -Scope '/' -RoleDefinitionName 'Owner' -ObjectId $user.Id
```
> Please note: sometimes it can take up to 15 minutes for permission to propagate at tenant root scope. It is highly recommended that you log out and log back in to refresh the token before you proceed with the deployment.*
## Azure Resource Provider prerequisites
For the ALZ deployment, a number of resource providers must be registered on ALL subscriptions. Ensure that all the resource providers listed [here](https://github.com/Azure/Enterprise-Scale/wiki/ALZ-Resource-Provider-Recommendations) are registered before deploying Azure Landing Zones.
Please see [here](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) for details on how to register a resource provider should you need to do so.