You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-desktop/autoscale-scaling-plan.md
+38-52Lines changed: 38 additions & 52 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,8 @@ The autoscale feature (preview) lets you scale your Azure Virtual Desktop deploy
21
21
- Session limits per session host
22
22
23
23
>[!NOTE]
24
-
>Windows Virtual Desktop (classic) doesn't support the autoscale feature. It also doesn't support scaling ephemeral disks.
24
+
> - Azure Virtual Desktop (classic) doesn't support the autoscale feature.
25
+
> - Autsoscale doesn't support scaling of ephemeral disks.
25
26
26
27
For best results, we recommend using autoscale with VMs you deployed with Azure Virtual Desktop Azure Resource Manager templates or first-party tools from Microsoft.
27
28
@@ -30,7 +31,7 @@ For best results, we recommend using autoscale with VMs you deployed with Azure
30
31
>
31
32
> - You can only use autoscale in the Azure public cloud.
32
33
> - You can only configure autoscale with the Azure portal.
33
-
> - You can only deploy the scaling plan in the US and Europe regions.
34
+
> - You can only deploy the scaling plan to US and European regions.
34
35
35
36
## Requirements
36
37
@@ -44,8 +45,7 @@ Before you create your first scaling plan, make sure you follow these guidelines
44
45
45
46
To start creating a scaling plan, you'll first need to create a custom Role-based Access Control (RBAC) role in your subscription. This role will allow Windows Virtual Desktop to power manage all VMs in your subscription. It will also let the service apply actions on both host pools and VMs when there are no active user sessions.
46
47
47
-
To create the custom role, follow the instructions in [Azure custom roles](../role-based-access-control/custom-roles.md), using this JSON template:
48
-
48
+
To create the custom role, follow the instructions in [Azure custom roles](../role-based-access-control/custom-roles.md) while using the following JSON template. This template already includes any permissions you need. For more detailed instructions, see [Assign custom roles with the Azure portal](#assign-custom-roles-with-the-azure-portal).
49
49
```json
50
50
{
51
51
"properties": {
@@ -57,19 +57,20 @@ To create the custom role, follow the instructions in [Azure custom roles](../ro
@@ -120,29 +121,14 @@ To assign the custom role to grant access:
120
121
121
122
1. In the **Access control (IAM) tab**, select **Add role assignments**.
122
123
123
-
2. Select the role you just created.
124
+
2. Select the role you just created and continue to the next screen.
124
125
125
-
3. In the search bar, enter and select **Windows Virtual Desktop**, as shown in the following screenshot.
126
+
3. Select **+Select members**. In the search bar, enter and select **Windows Virtual Desktop**, as shown in the following screenshot. When you have a Azure Virtual Desktop (classic) deployment and an Azure Virtual Desktop with Azure Resource Manager Azure Virtual Desktop objects, you will see two apps with the same name. Select them both.
126
127
127
128
> [!div class="mx-imgBorder"]
128
129
> 
129
130
130
-
When adding the custom role in the Azure portal, make sure you've also selected the following permissions:
These are the same permissions you entered back in step 4.
131
+
4. Select **Review + assign** to complete the assignment.
146
132
147
133
## How creating a scaling plan works
148
134
@@ -189,7 +175,7 @@ To create a scaling plan:
189
175
190
176
6. Optionally, you can also add a "friendly" name that will be displayed to your users and a description for your plan.
191
177
192
-
7. For **Region**, select a region for your scaling plan. The metadata for the object will be stored in the geography associated with the region. Currently, autoscale only supports the Central US and East US 2 regions. To learn more about regions, see [Data locations](data-locations.md).
178
+
7. For **Region**, select a region for your scaling plan. The metadata for the object will be stored in the geography associated with the region. To learn more about regions, see [Data locations](data-locations.md).
193
179
194
180
8. For **Time zone**, select the time zone you'll use with your plan.
0 commit comments