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/ai-services/metrics-advisor/encryption.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,11 +69,11 @@ Metrics Advisor supports CMK and double encryption by using BYOS (bring your own
69
69
1. Set 'Allow access to Azure services' as 'Yes'.
70
70
2. Add your clientIP address to sign in to Azure Database for PostgreSQL.
71
71
72
-
- Get the access-token for your account with resource type 'https://server-name.database.windows.net'. The access token is the password you need to sign in to the Azure Database for PostgreSQL by your account. An example using `az` client:
72
+
- Get the access-token for your account with resource type 'https://ossrdbms-aad.database.windows.net'. The access token is the password you need to sign in to the Azure Database for PostgreSQL by your account. An example using `az` client:
73
73
74
74
```
75
75
az login
76
-
az account get-access-token --resource https://server-name.database.windows.net
76
+
az account get-access-token --resource https://ossrdbms-aad.database.windows.net
77
77
```
78
78
79
79
- After getting the token, use it to sign in to your Azure Database for PostgreSQL. Replace the 'servername' as the one that you can find in the 'overview' of your Azure Database for PostgreSQL.
Copy file name to clipboardExpand all lines: articles/app-service/tutorial-connect-msi-azure-database.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -197,7 +197,7 @@ If you encounter any problem when creating a connection, refer to [Troubleshooti
197
197
Connectivity to the Azure Database for MySQL in your code follows the `DefaultAzureCredential` pattern for all language stacks. `DefaultAzureCredential` is flexible enough to adapt to both the development environment and the Azure environment. When running locally, it can retrieve the logged-in Azure user from the environment of your choice (Visual Studio, Visual Studio Code, Azure CLI, or Azure PowerShell). When running in Azure, it retrieves the managed identity. So it's possible to have connectivity to database both at development time and in production. The pattern is as follows:
198
198
199
199
1. Instantiate a `DefaultAzureCredential` from the Azure Identity client library. If you're using a user-assigned identity, specify the client ID of the identity.
200
-
2. Get an access token for Azure Database for MySQL: `https://server-name.database.windows.net/.default`.
200
+
2. Get an access token for Azure Database for MySQL: `https://ossrdbms-aad.database.windows.net/.default`.
201
201
3. Add the token to your connection string.
202
202
4. Open the connection.
203
203
@@ -208,7 +208,7 @@ Connectivity to the Azure Database for MySQL in your code follows the `DefaultAz
208
208
Connectivity to the Azure Database for PostgreSQL in your code follows the `DefaultAzureCredential` pattern for all language stacks. `DefaultAzureCredential` is flexible enough to adapt to both the development environment and the Azure environment. When running locally, it can retrieve the logged-in Azure user from the environment of your choice (Visual Studio, Visual Studio Code, Azure CLI, or Azure PowerShell). When running in Azure, it retrieves the managed identity. So it's possible to have connectivity to database both at development time and in production. The pattern is as follows:
209
209
210
210
1. Instantiate a `DefaultAzureCredential` from the Azure Identity client library. If you're using a user-assigned identity, specify the client ID of the identity.
211
-
2. Get an access token for Azure Database for PostgreSQL: `https://server-name.database.windows.net/.default`.
211
+
2. Get an access token for Azure Database for PostgreSQL: `https://ossrdbms-aad.database.windows.net/.default`.
description: Answers to common questions about using Azure Resource Manager to manage resources.
5
5
ms.topic: faq
6
-
ms.date: 02/22/2024
6
+
ms.date: 05/31/2024
7
7
content_well_notification:
8
8
- AI-contribution
9
9
ai-usage: ai-assisted
@@ -35,12 +35,6 @@ sections:
35
35
resource group location, we recommend that you select a location close to where your control operations originate. Typically, this location is the one closest to
36
36
your current location.
37
37
38
-
- question: Can I move a resource group to a different subscription?
39
-
answer: |
40
-
No, you can't move a resource group to a new subscription. But, you can move all of the resources in the resource group to a resource group in another
41
-
subscription. Settings such as tags, role assignments, and policies aren't automatically transferred from the original resource group to the destination resource group.
42
-
You need to reapply these settings to the new resource group. For more information, see [Move resources to new resource group or subscription](./move-support-resources.md).
43
-
44
38
- name: Resources
45
39
questions:
46
40
- question: What happens if two operations update the same resource at the same time?
@@ -472,6 +472,10 @@ If the source or target resource group contains a virtual network, the states of
472
472
473
473
When you receive this error, you have two options. Either move your resources to a resource group that doesn't have a virtual network, or [contact support](../../azure-portal/supportability/how-to-create-azure-support-request.md).
474
474
475
+
**Question: Can I move a resource group to a different subscription?**
476
+
477
+
No, you can't move a resource group to a new subscription. But, you can move all of the resources in the resource group to a resource group in another subscription. Settings such as tags, role assignments, and policies aren't automatically transferred from the original resource group to the destination resource group. You need to reapply these settings to the new resource group. For more information, see [Move resources to new resource group or subscription](./move-support-resources.md).
478
+
475
479
## Next steps
476
480
477
481
For a list of which resources support move, see [Move operation support for resources](move-support-resources.md).
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/overview.md
+18-22Lines changed: 18 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Azure Resource Manager overview
3
3
description: Describes how to use Azure Resource Manager for deployment, management, and access control of resources on Azure.
4
4
ms.topic: overview
5
-
ms.date: 02/16/2024
5
+
ms.date: 05/31/2024
6
6
ms.custom: devx-track-arm-template
7
7
---
8
8
@@ -87,19 +87,7 @@ There are some important factors to consider when defining your resource group:
87
87
88
88
* You can move a resource from one resource group to another group. For more information, see [Move resources to new resource group or subscription](move-resource-group-and-subscription.md).
89
89
90
-
* The resources in a resource group can be located in different regions than the resource group.
91
-
92
-
* When you create a resource group, you need to provide a location for that resource group.
93
-
94
-
You may be wondering, "Why does a resource group need a location? And, if the resources can have different locations than the resource group, why does the resource group location matter at all?"
95
-
96
-
The resource group stores metadata about the resources. When you specify a location for the resource group, you're specifying where that metadata is stored. For compliance reasons, you may need to ensure that your data is stored in a particular region.
97
-
98
-
To ensure state consistency for the resource group, all [control plane operations](./control-plane-and-data-plane.md) are routed through the resource group's location. When selecting a resource group location, we recommend that you select a location close to where your control operations originate. Typically, this location is the one closest to your current location. This routing requirement only applies to control plane operations for the resource group. It doesn't affect requests that are sent to your applications.
99
-
100
-
If a resource group's region is temporarily unavailable, you may not be able to update resources in the resource group because the metadata is unavailable. The resources in other regions still function as expected, but you may not be able to update them. This condition may also apply to global resources like Azure DNS, Azure DNS Private Zones, Azure Traffic Manager, and Azure Front Door. You can view which types have their metadata managed by Azure Resource Manager via the [list of types for the Azure Resource Graph resources table](../../governance/resource-graph/reference/supported-tables-resources.md#resources).
101
-
102
-
For more information about building reliable applications, see [Designing reliable Azure applications](/azure/architecture/checklist/resiliency-per-service).
90
+
* The resources in a resource group can be located in different regions than the resource group, but we recommend that you use the same location. See [What location should I use for my resource group?](#what-location-should-i-use-for-my-resource-group)
103
91
104
92
* A resource group can be used to scope access control for administrative actions. To manage a resource group, you can assign [Azure Policies](../../governance/policy/overview.md), [Azure roles](../../role-based-access-control/role-assignments-portal.yml), or [resource locks](lock-resources.md).
105
93
@@ -115,6 +103,22 @@ There are some important factors to consider when defining your resource group:
115
103
116
104
* To create a resource group, you can use the [portal](manage-resource-groups-portal.md#create-resource-groups), [PowerShell](manage-resource-groups-powershell.md#create-resource-groups), [Azure CLI](manage-resource-groups-cli.md#create-resource-groups), or an [ARM template](../templates/deploy-to-subscription.md#resource-groups).
117
105
106
+
## What location should I use for my resource group?
107
+
108
+
When you create a resource group, you need to provide a location for that resource group.
109
+
110
+
You may be wondering, "Why does a resource group need a location? And, if the resources can have different locations than the resource group, why does the resource group location matter at all?"
111
+
112
+
The resource group stores metadata about the resources. When you specify a location for the resource group, you're specifying where that metadata is stored. For compliance reasons, you may need to ensure that your data is stored in a particular region.
113
+
114
+
To ensure state consistency for the resource group, all [control plane operations](./control-plane-and-data-plane.md) are routed through the resource group's location. When selecting a resource group location, we recommend that you select a location close to where your control operations originate. Typically, this location is the one closest to your current location. This routing requirement only applies to control plane operations for the resource group. It doesn't affect requests that are sent to your applications.
115
+
116
+
If a resource group's region is temporarily unavailable, you may not be able to update resources in the resource group because the metadata is unavailable. The resources in other regions still function as expected, but you may not be able to update them. This condition may also apply to global resources like Azure DNS, Azure DNS Private Zones, Azure Traffic Manager, and Azure Front Door. You can view which types have their metadata managed by Azure Resource Manager via the [list of types for the Azure Resource Graph resources table](../../governance/resource-graph/reference/supported-tables-resources.md#resources).
117
+
118
+
To reduce the impact of regional outages, we recommend that you locate resources in the same region as the resource group. When the resource group's region is unavailable, Azure Resource Manager is unable to update your resource's metadata and blocks your write calls. By colocating your resource and resource group region, you reduce the risk of region unavailability because your resources and metadata exist in one region instead of multiple regions.
119
+
120
+
For more information about building reliable applications, see [Designing reliable Azure applications](/azure/architecture/checklist/resiliency-per-service).
121
+
118
122
## Resiliency of Azure Resource Manager
119
123
120
124
The Azure Resource Manager service is designed for resiliency and continuous availability. Resource Manager and control plane operations (requests sent to `management.azure.com`) in the REST API are:
@@ -129,14 +133,6 @@ The Azure Resource Manager service is designed for resiliency and continuous ava
129
133
130
134
This resiliency applies to services that receive requests through Resource Manager. For example, Key Vault benefits from this resiliency.
131
135
132
-
## Resource group location alignment
133
-
134
-
To reduce the impact of regional outages, we recommend that you locate resources in the same region as the resource group.
135
-
136
-
The resource group location is where Azure Resource Manager stores metadata for the resources in the resource group. Azure Resource Manager uses this location for routing and caching. For example, when you list your resources at the subscription or resource group scopes, Azure Resource Manager gets the information from the cache.
137
-
138
-
When the resource group's region is unavailable, Azure Resource Manager is unable to update your resource's metadata and blocks your write calls. By colocating your resource and resource group region, you reduce the risk of region unavailability because your resources and metadata exist in one region instead of multiple regions.
139
-
140
136
## Resolve concurrent operations
141
137
142
138
When two or more operations try to update the same resource at the same time, Azure Resource Manager detects the conflict and permits only one operation to complete successfully. Azure Resource Manager blocks the other operations and returns an error.
0 commit comments