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/cost-management-billing/reservations/view-reservations.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,8 +26,6 @@ By default, the following users can view and manage reservations:
26
26
- A Reservation administrator for reservations in their Azure Active Directory (Azure AD) tenant (directory)
27
27
- A Reservation reader has read-only access to reservations in their Azure Active Directory tenant (directory)
28
28
29
-
Currently, the reservation administrator and reservation reader roles are only available to assign using PowerShell. They can't be viewed or assigned in the Azure portal. For more information, see [Grant access with PowerShell](#grant-access-with-powershell).
30
-
31
29
The reservation lifecycle is independent of an Azure subscription, so the reservation isn't a resource under the Azure subscription. Instead, it's a tenant-level resource with its own Azure RBAC permission separate from subscriptions. Reservations don't inherit permissions from subscriptions after the purchase.
32
30
33
31
## View and manage reservations
@@ -136,7 +134,14 @@ When you use the PowerShell script to assign the ownership role and it runs succ
136
134
## Tenant-level access
137
135
[User Access Administrator](../../role-based-access-control/built-in-roles.md#user-access-administrator) rights are required before you can grant users or groups the Reservation Administrator and Reservation Reader roles at the tenant level. In order to get User Access Administrator rights at the tenant level, follow [Elevate access](../../role-based-access-control/elevate-access-global-admin.md) steps.
138
136
139
-
## Add a Reservation Administrator role at the tenant level
137
+
## Add a Reservation Administrator role or Reservation Reader role at the tenant level
138
+
You can assign these roles from [Azure portal](https://portal.azure.com).
139
+
140
+
1. Sign in to the Azure portal and navigate to **Reservations**.
141
+
2. At the top of the page, select **Role Assignment**.
142
+
3. To make modifications, add user as a Reservation Administrator or Reservation Reader using Access control.
143
+
144
+
## Add a Reservation Administrator role at the tenant level using Azure PowerShell script
140
145
141
146
Use the following Azure PowerShell script to add a Reservation Administrator role at the tenant level with PowerShell.
Copy file name to clipboardExpand all lines: articles/virtual-desktop/move-resources.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,10 @@ In this article, we'll tell you how to move Azure Virtual Desktop resources betw
15
15
>This process doesn't perform an actual resource move. Instead, you delete the old resources and recreate them in the region you want to move the resources to. We recommend you test this process before using it on production workloads to understand how it will impact your deployment.
16
16
17
17
This process does not perform an actual resource move. Rather it does a delete and recreate in the new region which is different. Hence we recommend you test this process before using on production workloads to understand the impact of doing this.
18
+
> [!NOTE]
19
+
> This process does not perform an actual resource move. Rather it does a delete and recreate in the new region which is different. Hence we recommend you test this process before using on production workloads to understand the impact of doing this.
20
+
>
21
+
> The information in this article is applicable to all Azure Virtual Desktop resources, including host pools, application groups, scaling plans, and workspaces.
18
22
19
23
## Important information
20
24
@@ -24,9 +28,11 @@ When you move Azure Virtual Desktop resources between regions, these are some th
24
28
25
29
- Workspaces and their associated app groups also need to be in the same region.
26
30
31
+
- Scaling plans and the host pools they are assigned to also need to be in the same region.
32
+
27
33
- All resources to be moved have to be in the same resource group. Template exports require having resources in the same group, so if you want them to be in a different location, you'll need to modify the exported template to change the location of its resources.
28
34
29
-
- Once you're done moving your resources to a new region, you must delete the original resources. The resource ID of our resources won't change during the moving process, so there will be a name conflict with your old resources if you don't delete them.
35
+
- Once you're done moving your resources to a new region, you must delete the original resources. The resource ID of your resources won't change during the moving process, so there will be a name conflict with your old resources if you don't delete them.
30
36
31
37
- Existing session hosts attached to a host pool that you move will stop working. You'll need to recreate the session hosts in the new region.
32
38
@@ -56,7 +62,7 @@ To modify the template you exported:
56
62
57
63
2. In each resource inside the template file, find the "location" property and modify it to the location you want to move them to. For example, if your deployment's currently in the East US region but you want to move it to the West US region, you'd change the "eastus" location to "westus." Learn more about which Azure regions you can use at [Azure geographies](https://azure.microsoft.com/global-infrastructure/geographies/#geographies).
58
64
59
-
3.For each host pool, remove the "publicNetworkAccess" parameter, if present.
65
+
3.If you are moving a host pool, remove the "publicNetworkAccess" parameter, if present.
Copy file name to clipboardExpand all lines: articles/virtual-desktop/teams-on-avd.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,6 @@ manager: femila
9
9
---
10
10
# Use Microsoft Teams on Azure Virtual Desktop
11
11
12
-
>[!IMPORTANT]
13
-
>Media optimization for Teams is supported for Microsoft 365 Government (GCC) and GCC-High environments. Media optimization for Teams isn't supported for Microsoft 365 DoD.
14
-
15
12
>[!NOTE]
16
13
>Media optimization for Microsoft Teams is only available for the following two clients:
17
14
>
@@ -48,7 +45,7 @@ To enable media optimization for Teams, set the following registry key on the ho
48
45
49
46
### Install the Teams WebSocket Service
50
47
51
-
Install the latest version of the [Remote Desktop WebRTC Redirector Service](https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE4YM8L) on your VM image. If you encounter an installation error, install the [latest Microsoft Visual C++ Redistributable](https://support.microsoft.com/help/2977003/the-latest-supported-visual-c-downloads) and try again.
48
+
Install the latest version of the [Remote Desktop WebRTC Redirector Service](https://aka.ms/msrdcwebrtcsvc/msi) on your VM image. If you encounter an installation error, install the [latest Microsoft Visual C++ Redistributable](https://support.microsoft.com/help/2977003/the-latest-supported-visual-c-downloads) and try again.
0 commit comments