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/app-service/app-service-configure-premium-v4-tier.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -141,7 +141,7 @@ If your app runs where Premium v4 isn't available (either the deployment or the
141
141
142
142
When creating the plan, select the desired Premium v4 tier. This ensures the plan is in a deployment unit supporting Premium V4. Then, redeploy your application code to the new app. Even if you scale the new plan down to save costs, you can always scale back up to Premium v4 because the deployment unit supports it.
143
143
144
-
- Use the **Development tools** > **Clone app** page to create an App Service plan with Premium v4 in your desired region, specifying the app settings and configuration to clone.
144
+
- Use the **Development tools** > **Clone app** page to create an App Service plan with Premium v4 in your desired region, specifying the app settings and configuration to clone. Refer to the [current restrictions](app-service-web-app-cloning.md#current-restrictions) for app cloning.
145
145
146
146
:::image type="content" source="media/app-service-configure-premium-tier/clone-app.png" alt-text="Screenshot showing how to clone your app.":::
Copy file name to clipboardExpand all lines: articles/artifact-signing/how-to-signing-integrations.md
+14-6Lines changed: 14 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -146,21 +146,29 @@ To sign by using Artifact Signing, you need to provide the details of your Artif
146
146
"CorrelationId": "<Optional CorrelationId value>"
147
147
}
148
148
```
149
+
<sup>1</sup> The optional `"CorrelationId"` field is an opaque string value that you can provide to correlate sign requests with your own workflows, such as build identifiers or machine names.
149
150
150
151
> [!IMPORTANT]
151
152
> The `"Endpoint"` URI value must match the region where you created your Artifact Signing account **and** the certificate profile. Use one of the region-specific URIs in the table below. A region/endpoint mismatch commonly causes a 403 Forbidden error and an internal `SignerSign()` failure during signing.
152
153
153
154
| Region | Region class fields | Endpoint URI value |
154
155
|--------------|-----------|------------|
156
+
| Brazil South | BrazilSouth |`https://brs.codesigning.azure.net`|
157
+
| Central US | CentralUS |`https://cus.codesigning.azure.net`|
155
158
| East US | EastUS |`https://eus.codesigning.azure.net`|
156
-
| West US3 <sup>[1]</sup> | WestUS3 |`https://wus3.codesigning.azure.net`|
159
+
| Japan East | JapanEast |`https://jpe.codesigning.azure.net`|
160
+
| Korea Central | KoreaCentral |`https://krc.codesigning.azure.net`|
161
+
| North Central US | NorthCentralUS |`https://ncus.codesigning.azure.net`|
162
+
| North Europe | NorthEurope |`https://neu.codesigning.azure.net`|
163
+
| Poland Central | PolandCentral |`https://plc.codesigning.azure.net`|
164
+
| South Central US | SouthCentralUS |`https://scus.codesigning.azure.net`|
165
+
| Switzerland North | SwitzerlandNorth |`https://swn.codesigning.azure.net`|
157
166
| West Central US | WestCentralUS |`https://wcus.codesigning.azure.net`|
167
+
| West Europe | WestEurope |`https://weu.codesigning.azure.net`|
168
+
| West US | WestUS |`https://wus.codesigning.azure.net`|
158
169
| West US 2 | WestUS2 |`https://wus2.codesigning.azure.net`|
159
-
| North Europe | NorthEurope |`https://neu.codesigning.azure.net`|
160
-
| West Europe | WestEurope |`https://weu.codesigning.azure.net`|
161
-
162
-
<sup>1</sup> The optional `"CorrelationId"` field is an opaque string value that you can provide to correlate sign requests with your own workflows, such as build identifiers or machine names.
163
-
170
+
| West US 3 | WestUS3 |`https://wus3.codesigning.azure.net`|
171
+
164
172
### Authentication
165
173
166
174
This Task performs authentication using [DefaultAzureCredential](/dotnet/api/azure.identity.defaultazurecredential), which attempts a series of authentication methods in order. If one method fails, it attempts the next one until authentication is successful.
Copy file name to clipboardExpand all lines: articles/artifact-signing/quickstart.md
+17-8Lines changed: 17 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -117,14 +117,23 @@ An Artifact Signing account is a logical container that holds identity validatio
117
117
118
118
You can create Artifact Signing resources only in Azure regions where the service is currently available. The following table lists the Azure regions that currently support Artifact Signing resources:
119
119
120
-
| Region | Region class fields | Endpoint URI value |
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/concept-enable-rbac.md
+61Lines changed: 61 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,5 +60,66 @@ Follow these steps to assign App Configuration Data roles to your credential.
60
60
3. On the **Members** tab, follow the wizard to select the credential you're granting access to and then select **Next**.
61
61
4. Finally, on the **Review + assign** tab, select **Review + assign** to assign the role.
62
62
63
+
## Configuring cloud-specific audience for Entra ID authentication
64
+
65
+
When using Entra ID and the following Azure App Configuration libraries in clouds other than Azure cloud, Azure Government, and Microsoft Azure operated by 21Vianet, an appropriate Entra ID audience must be configured to enable authentication.
66
+
67
+
### [.NET](#tab/dotnet)
68
+
69
+
The Audience for the target cloud must be configured for the following packages.
70
+
71
+
- Azure SDK for .NET: Azure.Data.AppConfiguration >= 1.6.0
In the **Azure SDK for .NET**, audience is configured by utilizing the following API calls:
75
+
76
+
* The ConfigurationClient constructor [accepts ConfigurationClientOptions](/dotnet/api/azure.data.appconfiguration.configurationclient.-ctor#azure-data-appconfiguration-configurationclient-ctor(system-uri-azure-core-tokencredential-azure-data-appconfiguration-configurationclientoptions))
77
+
* ConfigurationClientOptions allows [Audience](/dotnet/api/azure.data.appconfiguration.configurationclientoptions.audience#azure-data-appconfiguration-configurationclientoptions-audience) to be set
78
+
79
+
The following code snippet demonstrates how to instantiate a configuration client with a cloud-specific audience.
80
+
81
+
```
82
+
var configurationClient = new ConfigurationClient(
83
+
myStoreEndpoint,
84
+
new DefaultAzureCredential(),
85
+
new ConfigurationClientOptions
86
+
{
87
+
Audience = "{Cloud specific audience here}"
88
+
});
89
+
```
90
+
91
+
In the **.NET configuration provider**, audience is configured by utilizing the following API calls:
92
+
93
+
* AzureAppConfigurationOptions exposes a [ConfigureClientOptions](/dotnet/api/microsoft.extensions.configuration.azureappconfiguration.azureappconfigurationoptions.configureclientoptions#microsoft-extensions-configuration-azureappconfiguration-azureappconfigurationoptions-configureclientoptions(system-action((azure-data-appconfiguration-configurationclientoptions)))) method
94
+
95
+
The following code snippet demonstrates how to add the Azure App Configuration provider into a .NET application with a cloud-specific audience.
96
+
97
+
```
98
+
builder.AddAzureAppConfiguration(o =>
99
+
{
100
+
o.Connect(
101
+
myStoreEndpoint,
102
+
new DefaultAzureCredential());
103
+
104
+
o.ConfigureClientOptions(clientOptions => clientOptions.Audience = "{Cloud specific audience here}");
105
+
});
106
+
```
107
+
108
+
---
109
+
110
+
### Audience
111
+
112
+
For Azure App Configuration in the global Azure cloud, use the following audience:
113
+
114
+
`https://appconfig.azure.com`
115
+
116
+
For Azure App Configuration in the national clouds, use the applicable audience specified in the table below:
Health Check | [GA](./reference-dotnet-provider.md#health-check) | GA | WIP | WIP | WIP | N/A
74
74
Select by Tag Filters | [GA](./reference-dotnet-provider.md#load-specific-key-values-using-selectors) | WIP | GA | GA | [GA](./reference-javascript-provider.md#tag-filters) | [GA](./reference-go-provider.md#tag-filters)
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/reference-dotnet-provider.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -651,6 +651,8 @@ For information about using snapshots, go to [Create and use snapshots](./howto-
651
651
652
652
A snapshot reference is a configuration setting that references a snapshot in the same App Configuration store. When loaded, the provider resolves it and adds all key-values from that snapshot. Using snapshot references enables switching between snapshots at runtime, unlike `SelectSnapshot("...")`, which requires code changes and/or restarts to switch to a new snapshot.
653
653
654
+
For more information about creating a snapshot reference, go to [snapshot reference concept](./concept-snapshot-references.md).
655
+
654
656
> [!NOTE]
655
657
> To use snapshot references, use the version *8.4.0* or later of `Microsoft.Extensions.Configuration.AzureAppConfiguration`.
A snapshot reference is a configuration setting that references a snapshot in the same App Configuration store. When loaded, the provider resolves it and adds all key-values from that snapshot. Using snapshot references enables switching between snapshots at runtime, unlike adding a snapshot selector, which requires code changes and/or restarts to switch to a new snapshot.
467
+
468
+
For more information about creating a snapshot reference, go to [snapshot reference concept](./concept-snapshot-references.md).
469
+
470
+
> [!NOTE]
471
+
> To use snapshot references, use the version *2.3.0* or later of `@azure/app-configuration-provider`.
472
+
464
473
## Startup retry
465
474
466
475
Configuration loading is a critical path operation during application startup. To ensure reliability, the Azure App Configuration provider implements a robust retry mechanism during the initial configuration load. This helps protect your application from transient network issues that might otherwise prevent successful startup.
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/rest-api-authentication-azure-ad.md
+1-11Lines changed: 1 addition & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,17 +39,7 @@ Before acquiring a Microsoft Entra token, you must identify what user you want t
39
39
40
40
Request the Microsoft Entra token with a proper audience. The audience can also be referred to as the *resource* that the token is being requested for.
41
41
42
-
For Azure App Configuration in the global Azure cloud, use the following audience:
43
-
44
-
`https://appconfig.azure.com`
45
-
46
-
For Azure App Configuration in the national clouds, use the applicable audience specified in the table below:
| Microsoft Azure operated by 21Vianet |`https://appconfig.azure.cn`|
52
-
| Bleu |`https://appconfig.sovcloud-api.fr`|
42
+
For details on which audience to use for which cloud, refer to the [audience section of the Entra ID access overview](./concept-enable-rbac.md#audience).
Copy file name to clipboardExpand all lines: articles/backup/azure-file-share-backup-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ ms.author: v-mallicka
16
16
17
17
Azure Files backup is a native cloud solution that protects your data and eliminates on-premises maintenance overheads. Azure Backup integrates with Azure File Sync, centralizing your File Share data and backups. The secure, managed backup solution supports **snapshot** and **vaulted** backups to protect your enterprise File Shares, ensuring data recovery from accidental or malicious deletion.
18
18
19
-
Azure Backup now offers general availability of Vaulted Backup for Azure Files (Standard tier), enabling secure, long-term protection with ransomware defense, cross-region recovery, and compliance-ready retention—all managed through a unified backup policy. For more insights, see the [Microsoft Community Hub blog](https://techcommunity.microsoft.com/blog/azurestorageblog/general-availability-vaulted-backup-for-azure-files---boost-your-data-security-a/4395344). To know the latest product enhancements and feature updates in Azure, see [Microsoft Azure Updates](https://azure.microsoft.com/updates?id=482659).
19
+
Azure Backup now offers general availability of Vaulted Backup for Azure Files, enabling secure, long-term protection with ransomware defense, cross-region recovery, and compliance-ready retention—all managed through a unified backup policy. For more insights, see the [Microsoft Community Hub blog](https://techcommunity.microsoft.com/blog/azurestorageblog/general-availability-vaulted-backup-for-azure-files---boost-your-data-security-a/4395344). To know the latest product enhancements and feature updates in Azure, see [Microsoft Azure Updates](https://azure.microsoft.com/updates?id=482659).
0 commit comments