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/create-fslogix-profile-container.md
+7-28Lines changed: 7 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,9 @@ The instructions in this guide are specifically for Azure Virtual Desktop users.
24
24
25
25
## Considerations
26
26
27
-
FSLogix profile containers on Azure NetApp Files can be accessed by users authenticating from Active Directory Domain Services (AD DS) and from [hybrid identities](../active-directory/hybrid/whatis-hybrid-identity.md), allowing Microsoft Entra users to access profile containers without requiring line-of-sight to domain controllers from Microsoft Entra hybrid joined and Microsoft Entra joined virtual machines (VMs). For more information, see [Access SMB volumes from Microsoft Entra joined Windows VMs](../azure-netapp-files/access-smb-volume-from-windows-client.md).
27
+
* To optimize performance and scalability, the number of _concurrent_ users accessing FSLogix profile containers stored on a single Azure NetApp Files regular volume should be limited to 3,000. Having more than 3,000 _concurrent_ users on a single volume causes significant increased latency on the volume. If your scenario requires more than 3,000 _concurrent_ users, divide users across multiple regular volumes or use a large volume. A single large volume can store FSLogix profiles for up to 50,000 _concurrent_ users. For more information on large volumes, see [Requirements and considerations for large volumes](../azure-netapp-files/large-volumes-requirements-considerations.md).
28
+
29
+
* FSLogix profile containers on Azure NetApp Files can be accessed by users authenticating from Active Directory Domain Services (AD DS) and from [hybrid identities](../active-directory/hybrid/whatis-hybrid-identity.md), allowing Microsoft Entra users to access profile containers without requiring line-of-sight to domain controllers from Microsoft Entra hybrid joined and Microsoft Entra joined virtual machines (VMs). For more information, see [Access SMB volumes from Microsoft Entra joined Windows VMs](../azure-netapp-files/access-smb-volume-from-windows-client.md).
28
30
29
31
## Prerequisites
30
32
@@ -39,45 +41,22 @@ To get started, you need to set up an Azure NetApp Files account.
39
41
40
42
1. Sign in to the [Azure portal](https://portal.azure.com). Make sure your account has contributor or administrator permissions.
41
43
42
-
2. Select the **Azure Cloud Shell icon** to the right of the search bar to open Azure Cloud Shell.
43
-
44
-
3. Once Azure Cloud Shell is open, select **PowerShell**.
45
-
46
-
4. If this is your first time using Azure Cloud Shell, create a storage account in the same subscription you keep your Azure NetApp Files and Azure Virtual Desktop.
47
-
48
-
> [!div class="mx-imgBorder"]
49
-
> 
50
-
51
-
5. Once Azure Cloud Shell loads, run the following two cmdlets.
52
-
53
-
```azurecli
54
-
az account set --subscription <subscriptionID>
55
-
```
56
-
57
-
```azurecli
58
-
az provider register --namespace Microsoft.NetApp --wait
59
-
```
60
-
61
-
6. In the left side of the window, select **All services**. Enter **Azure NetApp Files** into the search box that appears at the top of the menu.
44
+
1. In the left side of the window, select **All services**. Enter **Azure NetApp Files** into the search box that appears at the top of the menu.
62
45
63
46
> [!div class="mx-imgBorder"]
64
47
> 
65
48
66
49
67
-
7. Select **Azure NetApp Files** in the search results, then select **Create**.
50
+
1. Select **Azure NetApp Files** in the search results, then select **Create**.
68
51
69
-
8. Select the **Add** button.
70
-
9. When the **New NetApp account** tab opens, enter the following values:
52
+
1. When the **New NetApp account** tab opens, enter the following values:
71
53
72
54
- For **Name**, enter your NetApp account name.
73
55
- For **Subscription**, select the subscription for the storage account you set up in step 4 from the drop-down menu.
74
56
- For **Resource group**, either select an existing resource group from the drop-down menu or create a new one by selecting **Create new**.
75
57
- For **Location**, select the region for your NetApp account from the drop-down menu. This region must be the same region as your session host VMs.
76
58
77
-
>[!NOTE]
78
-
>Azure NetApp Files currently doesn't support mounting of a volume across regions.
79
-
80
-
10. When you're finished, select **Create** to create your NetApp account.
59
+
1. When you're finished, select **Create** to create your NetApp account.
0 commit comments