Skip to content

Commit 91adad9

Browse files
authored
Merge pull request #256424 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 9228990 + 0bd4a1e commit 91adad9

5 files changed

Lines changed: 7 additions & 5 deletions

File tree

articles/active-directory-b2c/custom-domain.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ description: Learn how to enable custom domains in your redirect URLs for Azure
55
services: active-directory-b2c
66
author: kengaderdus
77
manager: CelesteDG
8-
98
ms.service: active-directory
109
ms.workload: identity
1110
ms.topic: how-to
@@ -399,6 +398,9 @@ Copy the URL, change the domain name manually, and then paste it back to your br
399398

400399
Azure Front Door passes the user's original IP address. It's the IP address that you'll see in the audit reporting or your custom policy.
401400

401+
> [!IMPORTANT]
402+
> If the client sends an `x-forwarded-for` header to Azure Front Door, Azure AD B2C will use the originator's `x-forwarded-for` as the user's IP address for [Conditional Access Evaluation](./conditional-access-identity-protection-overview.md) and the `{Context:IPAddress}` [claims resolver](./claim-resolver-overview.md).
403+
402404
### Can I use a third-party Web Application Firewall (WAF) with B2C?
403405

404406
Yes, Azure AD B2C supports BYO-WAF (Bring Your Own Web Application Firewall). However, you must test WAF to ensure that it doesn't block or alert legitimate requests to Azure AD B2C user flows or custom policies. Learn how to configure [Akamai WAF](partner-akamai.md) and [Cloudflare WAF](partner-cloudflare.md) with Azure AD B2C.

articles/mysql/single-server/concepts-azure-ad-authentication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ Please note that management operations, such as adding new users, are only suppo
8080
## Additional considerations
8181

8282
- Microsoft Entra authentication is only available for MySQL 5.7 and newer.
83-
- Only one Microsoft Entra administrator can be configured for a Azure Database for MySQL server at any time.
83+
- Only one Microsoft Entra administrator can be configured for an Azure Database for MySQL server at any time.
8484
- Only a Microsoft Entra administrator for MySQL can initially connect to the Azure Database for MySQL using a Microsoft Entra account. The Active Directory administrator can configure subsequent Microsoft Entra database users.
8585
- If a user is deleted from Microsoft Entra ID, that user will no longer be able to authenticate with Microsoft Entra ID, and therefore it will no longer be possible to acquire an access token for that user. In this case, although the matching user will still be in the database, it will not be possible to connect to the server with that user.
8686
> [!NOTE]

articles/mysql/single-server/concepts-data-access-security-private-link.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ Clients can connect to the private endpoint from the same VNet, [peered VNet](..
9292
Configure [VNet peering](../../virtual-network/tutorial-connect-virtual-networks-powershell.md) to establish connectivity to the Azure Database for MySQL from an Azure VM in a peered VNet.
9393

9494
### Connecting from an Azure VM in VNet-to-VNet environment
95-
Configure [VNet-to-VNet VPN gateway connection](../../vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-portal.md) to establish connectivity to a Azure Database for MySQL from an Azure VM in a different region or subscription.
95+
Configure [VNet-to-VNet VPN gateway connection](../../vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-portal.md) to establish connectivity to an Azure Database for MySQL from an Azure VM in a different region or subscription.
9696

9797
### Connecting from an on-premises environment over VPN
9898
To establish connectivity from an on-premises environment to the Azure Database for MySQL, choose and implement one of the options:

articles/private-link/private-endpoint-dns.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ For Azure services, use the recommended zone names as described in the following
8888
| SignalR (Microsoft.SignalRService/SignalR) | signalR | privatelink.service.signalr.net | service.signalr.net |
8989
| Azure Monitor (Microsoft.Insights/privateLinkScopes) | azuremonitor | privatelink.monitor.azure.com<br/> privatelink.oms.opinsights.azure.com <br/> privatelink.ods.opinsights.azure.com <br/> privatelink.agentsvc.azure-automation.net <br/> privatelink.blob.core.windows.net | monitor.azure.com<br/> oms.opinsights.azure.com<br/> ods.opinsights.azure.com<br/> agentsvc.azure-automation.net <br/> blob.core.windows.net |
9090
| Azure AI services (Microsoft.CognitiveServices/accounts) | account | privatelink.cognitiveservices.azure.com <br/> privatelink.openai.azure.com | cognitiveservices.azure.com <br/> openai.azure.com |
91-
| Azure File Sync (Microsoft.StorageSync/storageSyncServices) | afs | {regionName}.privatelink.afs.azure.net | {regionName}.afs.azure.net |
91+
| Azure File Sync (Microsoft.StorageSync/storageSyncServices) | afs | privatelink.afs.azure.net | afs.azure.net |
9292
| Azure Data Factory (Microsoft.DataFactory/factories) | dataFactory | privatelink.datafactory.azure.net | datafactory.azure.net |
9393
| Azure Data Factory (Microsoft.DataFactory/factories) | portal | privatelink.adf.azure.com | adf.azure.com |
9494
| Azure Cache for Redis (Microsoft.Cache/Redis) | redisCache | privatelink.redis.cache.windows.net | redis.cache.windows.net |

includes/azure-storage-account-limits-standard.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Microsoft recommends that you use a GPv2 storage account for most scenarios. You
2222
| Maximum number of storage accounts with standard endpoints per region per subscription, including standard and premium storage accounts. | 250 by default, 500 by request<sup>1</sup> |
2323
| Maximum number of storage accounts with Azure DNS zone endpoints (preview) per region per subscription, including standard and premium storage accounts. | 5000 (preview) |
2424
| Default maximum storage account capacity | 5 PiB <sup>2</sup> |
25-
| Maximum number of blob containers, blobs, file shares, tables, queues, entities, or messages per storage account. | No limit |
25+
| Maximum number of blob containers, blobs, directories and subdirectories (if Hierarchical Namespace is enabled), file shares, tables, queues, entities, or messages per storage account. | No limit |
2626
| Default maximum request rate per storage account | 20,000 requests per second<sup>2</sup> |
2727
| Default maximum ingress per general-purpose v2 and Blob storage account in the following regions:<br /><ul><li>East Asia</li><li>Southeast Asia</li><li>Australia East</li><li>Brazil South</li><li>Canada Central</li><li>China East 2</li><li>China North 3</li><li>North Europe</li><li>West Europe</li><li>France Central</li><li>Germany West Central</li><li>Central India</li><li>Japan East</li><li>Jio India West</li><li>Korea Central</li><li>Norway East</li><li>South Africa North</li><li>Sweden Central</li><li>UAE North</li><li>UK South</li><li>Central US</li><li>East US</li><li>East US 2</li><li>USGov Virginia</li><li>USGov Arizona</li><li>North Central US</li><li>South Central US</li><li>West US</li><li>West US 2</li><li>West US 3</li></ul>| 60 Gbps<sup>2</sup> |
2828
| Default maximum ingress per general-purpose v2 and Blob storage account in regions that aren't listed in the previous row. | 25 Gbps<sup>2</sup> |

0 commit comments

Comments
 (0)