Skip to content

Commit e0daae3

Browse files
committed
Created include to avoid duplication
1 parent fd49b8f commit e0daae3

4 files changed

+79
-82
lines changed

azure-local/deploy/deployment-arc-register-configurator-app.md

Lines changed: 3 additions & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -25,15 +25,7 @@ Before you begin, make sure that you complete the following prerequisites:
2525

2626
### Azure Local machine prerequisites
2727

28-
1. Procure the hardware that you intend to use as an Azure Local system. Turn on these machines and connect them to the network.
29-
30-
1. Complete [prerequisites for your environment](../deploy/deployment-prerequisites.md).
31-
32-
1. [Prepare Active Directory](../deploy/deployment-prep-active-directory.md).
33-
34-
1. [Download the English-language Preview ISO](https://aka.ms/HCIReleaseImage).
35-
36-
1. Use the downloaded Preview ISO and follow the steps for operating system installation in [Install Azure Stack HCI Operating System, version 23H2](../deploy/deployment-install-os.md).
28+
[!INCLUDE [hci-registration-azure-local-machine-prerequisites](../includes/hci-registration-azure-local-machine-prerequisites.md)]
3729

3830
1. Download the [Configurator App for Azure Local](https://aka.ms/ConfiguratorAppForHCI).
3931

@@ -44,29 +36,7 @@ Before you begin, make sure that you complete the following prerequisites:
4436

4537
### Azure prerequisites
4638

47-
1. **Register required resource providers.** Make sure that your Azure subscription is registered against the required resource providers. To register, you must be an owner or contributor on your subscription. You can also ask an administrator to register.
48-
49-
Run the following [PowerShell commands](/azure/azure-resource-manager/management/resource-providers-and-types#azure-powershell) to register:
50-
51-
```powershell
52-
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.HybridCompute"
53-
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.GuestConfiguration"
54-
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.HybridConnectivity"
55-
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.AzureStackHCI"
56-
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.Kubernetes"
57-
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.KubernetesConfiguration"
58-
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.ExtendedLocation"
59-
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.ResourceConnector"
60-
Register-ResourceProviderIfRequired -ProviderNamespace "HybridContainerService"
61-
```
62-
63-
1. **Create a resource group**. Follow the steps to [Create a resource group](/azure/azure-resource-manager/management/manage-resource-groups-portal#create-resource-groups) where you want to register your machines. Make a note of the resource group name and the associated subscription ID.
64-
65-
1. **Get the tenant ID**. Follow the steps in [Get the tenant ID of your Microsoft Entra tenant through the Azure portal](/azure/azure-portal/get-subscription-tenant-id):
66-
67-
1. In the Azure portal, go to **Microsoft Entra ID** > **Properties**.
68-
69-
1. Scroll down to the Tenant ID section and copy the **Tenant ID** value to use later.
39+
[!INCLUDE [hci-registration-azure-prerequisites](../includes/hci-registration-azure-prerequisites.md)]
7040

7141
1. **Get Arc gateway ID**. Skip this step if you didn't set up Azure Arc gateway. If you [Set up an Azure Arc gateway](../deploy/deployment-azure-arc-gateway-overview.md#create-the-arc-gateway-resource-in-azure), get the resource ID of the Arc gateway. This is also referred to as the `ArcGatewayID`.
7242

@@ -77,22 +47,7 @@ Before you begin, make sure that you complete the following prerequisites:
7747
```
7848
7949
1. Make a note of the Arc gateway ID to use later.
80-
81-
1. **Verify permissions**. As you register machines as Arc resources, make sure that you're either the resource group owner or have the following permissions on the resource group where the machines are provisioned:
82-
83-
- `Azure Connected Machine Onboarding`.
84-
- `Azure Connected Machine Resource Administrator`.
85-
86-
To verify that you have these roles, follow these steps in the Azure portal:
87-
88-
1. Go to the subscription you used for the Azure Local deployment.
89-
90-
1. Go to the resource group where you plan to register the machine.
91-
92-
1. In the left-pane, go to **Access Control (IAM)**.
93-
94-
1. In the right-pane, go to **Role assignments**. Verify that you have `Azure Connected Machine Onboarding` and `Azure Connected Machine Resource Administrator` roles assigned.
95-
50+
9651
## Step 1: Configure the network and connect to Azure
9752
9853
Follow these steps to configure network settings and connect the machines to Azure. Start this action a few minutes after you turn on the machine.

azure-local/deploy/deployment-arc-register-server-permissions.md

Lines changed: 4 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -19,43 +19,13 @@ This article describes how to register your Azure Local machines and then set up
1919

2020
Before you begin, make sure you've completed the following prerequisites:
2121

22-
- Satisfy the [prerequisites and complete deployment checklist](./deployment-prerequisites.md).
23-
- Prepare your [Active Directory](./deployment-prep-active-directory.md) environment.
24-
- [Install the Azure Stack HCI operating system, version 23H2](./deployment-install-os.md) on each machine.
25-
26-
- Register your subscription with the required resource providers (RPs). You can use either the [Azure portal](/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider-1) or the [Azure PowerShell](/azure/azure-resource-manager/management/resource-providers-and-types#azure-powershell) to register. You need to be an owner or contributor on your subscription to register the following resource RPs:
27-
28-
- *Microsoft.HybridCompute*
29-
- *Microsoft.GuestConfiguration*
30-
- *Microsoft.HybridConnectivity*
31-
- *Microsoft.AzureStackHCI*
32-
- Microsoft.Kubernetes
33-
- Microsoft.KubernetesConfiguration
34-
- *Microsoft.ExtendedLocation*
35-
- *Microsoft.ResourceConnector*
36-
- *HybridContainerService*
22+
### Azure Local machine prerequisites
3723

38-
> [!NOTE]
39-
> The assumption is that the person registering the Azure subscription with the resource providers is a different person than the one who is registering the Azure Local machines with Arc.
40-
41-
- If you're registering the machines as Arc resources, make sure that you have the following permissions on the resource group where the machines were provisioned:
42-
43-
- Azure Connected Machine Onboarding
44-
- Azure Connected Machine Resource Administrator
45-
46-
To verify that you have these roles, follow these steps in the Azure portal:
47-
48-
1. Go to the subscription that you use for the Azure Local deployment.
49-
1. Go to the resource group where you're planning to register the machines.
50-
1. In the left-pane, go to **Access Control (IAM)**.
51-
1. In the right-pane, go the **Role assignments**. Verify that you have the **Azure Connected Machine Onboarding** and **Azure Connected Machine Resource Administrator** roles assigned.
24+
[!INCLUDE [hci-registration-azure-local-machine-prerequisites](../includes/hci-registration-azure-local-machine-prerequisites.md)]
5225

53-
<!--:::image type="content" source="media/deployment-arc-register-server-permissions/contributor-user-access-administrator-permissions.png" alt-text="Screenshot of the roles and permissions assigned in the deployment subscription." lightbox="./media/deployment-arc-register-server-permissions/contributor-user-access-administrator-permissions.png":::-->
26+
### Azure prerequisites
5427

55-
- Check your Azure policies. Make sure that:
56-
- The Azure policies aren't blocking the installation of extensions.
57-
- The Azure policies aren't blocking the creation of certain resource types in a resource group.
58-
- The Azure policies aren't blocking the resource deployment in certain locations.
28+
[!INCLUDE [hci-registration-azure-prerequisites](../includes/hci-registration-azure-prerequisites.md)]
5929

6030
## Register machines with Azure Arc
6131

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
author: alkohli
3+
ms.author: alkohli
4+
ms.service: azure-local
5+
ms.topic: include
6+
ms.date: 03/20/2025
7+
ms.reviewer: alkohli
8+
ms.lastreviewed: 03/20/2025
9+
---
10+
11+
- Complete [prerequisites and complete deployment checklist for your environment](../includes/../deploy/deployment-prerequisites.md).
12+
- Prepare [Active Directory](./deployment-prep-active-directory.md) environment.
13+
- Download the software and [Install the Azure Stack HCI operating system, version 23H2](../includes/../deploy/deployment-install-os.md) on each machine.
14+
15+
Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
author: alkohli
3+
ms.author: alkohli
4+
ms.service: azure-local
5+
ms.topic: include
6+
ms.date: 03/20/2025
7+
ms.reviewer: alkohli
8+
ms.lastreviewed: 03/20/2025
9+
---
10+
11+
12+
- **Register required resource providers.** Make sure that your Azure subscription is registered against the required resource providers. To register, you must be an owner or contributor on your subscription. You can also ask an administrator to register.
13+
14+
Run the following [PowerShell commands](/azure/azure-resource-manager/management/resource-providers-and-types#azure-powershell) to register:
15+
16+
```powershell
17+
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.HybridCompute"
18+
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.GuestConfiguration"
19+
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.HybridConnectivity"
20+
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.AzureStackHCI"
21+
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.Kubernetes"
22+
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.KubernetesConfiguration"
23+
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.ExtendedLocation"
24+
Register-ResourceProviderIfRequired -ProviderNamespace "Microsoft.ResourceConnector"
25+
Register-ResourceProviderIfRequired -ProviderNamespace "HybridContainerService"
26+
```
27+
28+
> [!NOTE]
29+
> The assumption is that the person registering the Azure subscription with the resource providers is a different person than the one who is registering the Azure Local machines with Arc.
30+
31+
1. **Create a resource group**. Follow the steps to [Create a resource group](/azure/azure-resource-manager/management/manage-resource-groups-portal#create-resource-groups) where you want to register your machines. Make a note of the resource group name and the associated subscription ID.
32+
33+
1. **Get the tenant ID**. Follow the steps in [Get the tenant ID of your Microsoft Entra tenant through the Azure portal](/azure/azure-portal/get-subscription-tenant-id):
34+
35+
1. In the Azure portal, go to **Microsoft Entra ID** > **Properties**.
36+
37+
1. Scroll down to the Tenant ID section and copy the **Tenant ID** value to use later.
38+
39+
1. **Verify permissions**. As you register machines as Arc resources, make sure that you're either the resource group owner or have the following permissions on the resource group where the machines are provisioned:
40+
41+
- `Azure Connected Machine Onboarding`.
42+
- `Azure Connected Machine Resource Administrator`.
43+
44+
To verify that you have these roles, follow these steps in the Azure portal:
45+
46+
1. Go to the subscription you used for the Azure Local deployment.
47+
48+
1. Go to the resource group where you plan to register the machine.
49+
50+
1. In the left-pane, go to **Access Control (IAM)**.
51+
52+
1. In the right-pane, go to **Role assignments**. Verify that you have `Azure Connected Machine Onboarding` and `Azure Connected Machine Resource Administrator` roles assigned.
53+
54+
- Check your Azure policies. Make sure that:
55+
- The Azure policies aren't blocking the installation of extensions.
56+
- The Azure policies aren't blocking the creation of certain resource types in a resource group.
57+
- The Azure policies aren't blocking the resource deployment in certain locations.

0 commit comments

Comments
 (0)