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/application-gateway/secure-application-gateway.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: mbender
6
6
ms.service: azure-application-gateway
7
7
ms.topic: concept-article
8
8
ms.custom: security
9
-
ms.date: 07/29/2025
9
+
ms.date: 08/15/2025
10
10
ai-usage: ai-assisted
11
11
---
12
12
@@ -54,7 +54,7 @@ Proper authentication and authorization controls ensure only authorized users an
54
54
55
55
Data protection for Application Gateway focuses on securing data in transit and managing certificates and secrets properly.
56
56
57
-
***Enable TLS encryption**: Configure TLS termination to encrypt data in transit between clients and your Application Gateway. Use TLS v1.2 or later and disable legacy versions like SSL 3.0 and TLS v1.0 to protect against known vulnerabilities. For more information, see [Overview of TLS termination and end to end TLS with Application Gateway](./ssl-overview.md).
57
+
***Enable TLS encryption**: Configure TLS termination to encrypt data in transit between clients and your Application Gateway. Ensure you are using the latest version to protect against known vulnerabilities. For more information, see [Overview of TLS termination and end to end TLS with Application Gateway](./ssl-overview.md).
58
58
59
59
***Store certificates in Azure Key Vault**: Use Azure Key Vault to securely store and manage your TLS certificates instead of embedding them in configuration files. This enables automatic certificate rotation and centralized management of secrets. For more information, see [TLS termination with Key Vault certificates](./key-vault-certs.md).
60
60
@@ -90,4 +90,4 @@ Asset management ensures your Application Gateway configurations are properly mo
90
90
91
91
- Learn more about [Azure security architecture and design](/azure/well-architected/security/)
92
92
- Review [Security in the Microsoft Cloud Adoption Framework](/azure/cloud-adoption-framework/secure/overview)
93
-
- Explore [Web Application Firewall on Azure Application Gateway](/azure/web-application-firewall/ag/ag-overview)
93
+
- Explore [Web Application Firewall on Azure Application Gateway](/azure/web-application-firewall/ag/ag-overview)
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/overview.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -137,6 +137,11 @@ Resource Manager is designed for resiliency and continuous availability. Resourc
137
137
138
138
This resiliency applies to services that receive requests through Resource Manager. Azure Key Vault is one service that benefits from this consistency.
139
139
140
+
141
+
Using the global endpoint `management.azure.com` is recommended for Azure Resource Manager routing because it enables DNS-based traffic distribution, automatic failover, and optimal routing to the closest or healthiest region, which improves latency and reliability for users worldwide.
142
+
Global endpoints typically result in faster response times, as users are directed to the nearest available region, reducing network hops and delays.
143
+
144
+
140
145
## Resolve concurrent operations
141
146
142
147
Concurrent resource updates can cause unexpected results. When two or more operations try to update the same resource at the same time, Resource Manager detects the conflict, allows only one operation to complete successfully, blocks the other operations, and returns an error. This resolution ensures that your updates are conclusive and reliable; you know the status of your resources and avoid any inconsistency or data loss.
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/identity/includes/entra-id/support-entra-id-users-js.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
@@ -134,13 +134,13 @@ From the project directory:
134
134
135
135
export default App;
136
136
```
137
-
You can import any implementation of the [TokenCredential](https://learn.microsoft.com/javascript/api/%40azure/core-auth/tokencredential) interface from the [Azure Identity SDK for JavaScript](https://www.npmjs.com/package/@azure/identity) to authenticate with Microsoft Entra ID. In this quickstart, we use the `InteractiveBrowserCredential` class, which is suitable for browser basic authentication scenarios. For a full list of the credentials offered, see [Credential Classes](https://learn.microsoft.com/javascript/api/overview/azure/identity-readme#credential-classes).
137
+
You can import any implementation of the [TokenCredential](/javascript/api/%40azure/core-auth/tokencredential) interface from the [Azure Identity SDK for JavaScript](https://www.npmjs.com/package/@azure/identity) to authenticate with Microsoft Entra ID. In this quickstart, we use the `InteractiveBrowserCredential` class, which is suitable for browser basic authentication scenarios. For a full list of the credentials offered, see [Credential Classes](/javascript/api/overview/azure/identity-readme#credential-classes).
### Step 1: Initialize implementation of TokenCredential from Azure Identity SDK
142
142
143
-
The first step in obtaining Communication Services access token for Entra ID user is getting an Entra ID access token for your Entra ID user by using [Azure Identity](https://learn.microsoft.com/javascript/api/overview/azure/identity-readme) SDK. To enable authentication for users across multiple tenants, initialize the `InteractiveBrowserCredential` class with the authority set to `https://login.microsoftonline.com/organizations`. For more information, see [Authority](https://learn.microsoft.com//entra/identity-platform/msal-client-application-configuration#authority).
143
+
The first step in obtaining Communication Services access token for Entra ID user is getting an Entra ID access token for your Entra ID user by using [Azure Identity](/javascript/api/overview/azure/identity-readme) SDK. To enable authentication for users across multiple tenants, initialize the `InteractiveBrowserCredential` class with the authority set to `https://login.microsoftonline.com/organizations`. For more information, see [Authority](/entra/identity-platform/msal-client-application-configuration#authority).
144
144
145
145
```javascript
146
146
// Initialize InteractiveBrowserCredential for use with AzureCommunicationTokenCredential.
### Step 1: Initialize implementation of TokenCredential from Azure Identity SDK
79
79
80
-
The first step in obtaining Communication Services access token for Entra ID user is getting an Entra ID access token for your Entra ID user by using [Azure.Identity](https://learn.microsoft.com/dotnet/api/overview/azure/identity-readme?view=azure-dotnet) SDK. The code below retrieves the Contoso Entra client ID and the Fabrikam tenant ID from environment variables named `ENTRA_CLIENT_ID` and `ENTRA_TENANT_ID`. To enable authentication for users across multiple tenants, initialize the `InteractiveBrowserCredential` class with the authority set to `https://login.microsoftonline.com/organizations`. For more information, see [Authority](https://learn.microsoft.com/entra/identity-platform/msal-client-application-configuration#authority).
80
+
The first step in obtaining Communication Services access token for Entra ID user is getting an Entra ID access token for your Entra ID user by using [Azure.Identity](/dotnet/api/overview/azure/identity-readme) SDK. The code below retrieves the Contoso Entra client ID and the Fabrikam tenant ID from environment variables named `ENTRA_CLIENT_ID` and `ENTRA_TENANT_ID`. To enable authentication for users across multiple tenants, initialize the `InteractiveBrowserCredential` class with the authority set to `https://login.microsoftonline.com/organizations`. For more information, see [Authority](/entra/identity-platform/msal-client-application-configuration#authority).
81
81
82
82
```csharp
83
83
// This code demonstrates how to fetch your Microsoft Entra client ID and tenant ID from environment variables.
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/identity/microsoft-entra-id-authentication-integration.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ This quickstart demonstrates how to use the Communication Services Common SDK al
23
23
## Prerequisites
24
24
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
25
25
- An active Azure Communication Services resource and endpoint URI. For more information, see [Create an Azure Communication Services resource](../create-communication-resource.md).
26
-
- A Microsoft Entra ID instance. For more information, see [Microsoft Entra ID overview](https://learn.microsoft.com/entra/fundamentals/whatis?source=docs).
26
+
- A Microsoft Entra ID instance. For more information, see [Microsoft Entra ID overview](/entra/fundamentals/whatis?source=docs).
27
27
28
28
## Introduction
29
29
@@ -49,7 +49,7 @@ The Administrator role has extended permissions in Microsoft Entra ID. Members o
49
49
To enable the Contoso application to access Azure Communication Services Clients application API permissions, the Contoso Administrator must create a service principal for Azure Communication Services Clients application in the Contoso Microsoft Entra ID tenant.
50
50
The Contoso Administrator can create a service principal in Contoso tenant by one of the following methods:
51
51
52
-
- Use the [Microsoft Graph REST API](https://learn.microsoft.com/graph/api/serviceprincipal-post-serviceprincipals?view=graph-rest-1.0&tabs=http#request) to run the following request:
52
+
- Use the [Microsoft Graph REST API](/graph/api/serviceprincipal-post-serviceprincipals#request) to run the following request:
53
53
54
54
```http
55
55
POST https://graph.microsoft.com/v1.0/servicePrincipals
@@ -62,7 +62,7 @@ Content-Type: application/json
62
62
63
63
This request can also be executed in [Graph Explorer](https://developer.microsoft.com/graph/graph-explorer/). Make sure to include your full tenant domain in the URL `https://developer.microsoft.com/graph/graph-explorer?tenant={tenant domain}`, sign in, and provide consent for `Application.ReadWrite.All` permission.
64
64
65
-
- Use the [Azure CLI](https://learn.microsoft.com/cli/azure/ad/sp?view=azure-cli-latest#az-ad-sp-create) to run the following command:
65
+
- Use the [Azure CLI](/cli/azure/ad/sp#az-ad-sp-create) to run the following command:
66
66
67
67
```azurecli-interactive
68
68
az ad sp create --id 2a04943b-b6a7-4f65-8786-2bb6131b59f6
@@ -205,4 +205,4 @@ In this quickstart, you learned how to:
205
205
Learn about the following concepts:
206
206
207
207
-[Support Microsoft Entra ID users in Azure Communication Services](../../concepts/identity-model.md#microsoft-entra-id-integrating-with-entra-id)
208
-
-[Tenancy in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/single-and-multi-tenant-apps)
208
+
-[Tenancy in Microsoft Entra ID](/entra/identity-platform/single-and-multi-tenant-apps)
Copy file name to clipboardExpand all lines: articles/event-grid/troubleshoot-subscription-validation.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
@@ -11,8 +11,8 @@ During event subscription creation, if you're seeing an error message such as `T
11
11
12
12
- Do an HTTP POST to your webhook url with a [sample SubscriptionValidationEvent](end-point-validation-event-grid-events-schema.md#validation-details) request body using curl or similar tool.
13
13
- If your webhook is implementing synchronous validation handshake mechanism, verify that the ValidationCode is returned as part of the response.
14
-
- If your webhook is implementing asynchronous validation handshake mechanism, verify that you're the HTTP POST is returning 200 OK.
15
-
- If your webhook is returning `403 (Forbidden)` in the response, check if your webhook is behind an Azure Application Gateway or Web Application Firewall. If it is, then your need to disable these firewall rules and do an HTTP POST again:
14
+
- If your webhook is implementing asynchronous validation handshake mechanism, verify that your POST endpoint is returning 200 OK.
15
+
- If your webhook is returning `403 (Forbidden)` in the response, check if your webhook is behind an Azure Application Gateway or Web Application Firewall. If it is, then you need to disable these firewall rules and do an HTTP POST again:
16
16
- 920300 (Request missing an accept header)
17
17
- 942430 (Restricted SQL character anomaly detection (args): # of special characters exceeded (12))
0 commit comments