Merge pull request #294733 from MicrosoftDocs/main

2/17/2025 11:00 AM IST Publish

Author: PhilKang0704

articles/application-gateway/custom-error.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 12/19/2023
+ms.date: 01/27/2025
 ms.author: jaysoni 
 ms.custom: devx-track-azurepowershell
 ---
@@ -23,17 +23,17 @@ The custom error pages are supported for the following response codes:
 
 | Response code | Description |
 | ---------- | ---------- |
-| 400 | Bad request (In preview) |
+| 400 | Bad request |
 | 403 | Forbidden |
-| 405 | Method not allowed (In preview) |
-| 408 | Request timeout (In preview) |
-| 500 | Internal Server Error (In preview) |
+| 405 | Method not allowed |
+| 408 | Request timeout |
+| 500 | Internal Server Error |
 | 502 | Bad gateway |
-| 503 | Service unavailable (In preview) |
-| 504 | Gateway timeout (In preview) |
+| 503 | Service unavailable |
+| 504 | Gateway timeout |
 
 > [!Note]
-> - API version 2022-09-01 or later should be used to configure error pages for the new response codes (in preview).
+> - API version 2022-09-01 or later should be used to configure error pages for all available response codes.
 > - Response code 404 (Page not found) is currently unsupported.
 > - The custom error pages are displayed for response codes generated by Application Gateway. If an error originates from the backend server, it is passed along unmodified to the client.
 

articles/communication-services/concepts/service-limits.md

@@ -163,6 +163,13 @@ The following table lists limits for [Azure managed domains](../quickstarts/emai
 
 For all message size limits, consider that Base64 encoding increases the size of the message. You need to increase the size value to account for the message size increase that occurs after the message attachments and any other binary data are Base64 encoded. Base64 encoding increases the size of the message by about 33%, so the message size is about 33% larger than the message sizes before encoding. For example, if you specify a maximum message size value of approximately 10 MB, you can expect a realistic maximum message size value of approximately 7.5 MB.
 
+### Resource limits
+
+| Name | Limit |
+| --- | --- |
+| SenderUsername/Mailfrom resource per domain | 100 |
+| Domains linked to a Communication Service resource | 100 |
+
 ### Send attachments larger than 10 MB
 
 To email file attachments up to 30 MB, make a [support request](../support.md).

articles/data-factory/connector-microsoft-fabric-warehouse.md

@@ -7,7 +7,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.topic: conceptual
 ms.custom: synapse
-ms.date: 09/04/2024
+ms.date: 02/11/2025
 ---
 
 # Copy and transform data in Microsoft Fabric Warehouse using Azure Data Factory or Azure Synapse Analytics
@@ -469,7 +469,7 @@ The following COPY statement settings are supported under `allowCopyCommand` in
 
 When your source data is not natively compatible with COPY statement, enable data copying via an interim staging Azure Blob or Azure Data Lake Storage Gen2 (it can't be Azure Premium Storage). In this case, the service automatically converts the data to meet the data format requirements of COPY statement. Then it invokes COPY statement to load data into Microsoft Fabric Warehouse. Finally, it cleans up your temporary data from the storage. See [Staged copy](copy-activity-performance-features.md#staged-copy) for details about copying data via a staging.
 
-To use this feature, create an [Azure Blob Storage linked service](connector-azure-blob-storage.md#linked-service-properties) or [Azure Data Lake Storage Gen2 linked service](connector-azure-data-lake-storage.md#linked-service-properties) with **account key or system-managed identity authentication** that refers to the Azure storage account as the interim storage.
+To use this feature, create an [Azure Blob Storage linked service](connector-azure-blob-storage.md#linked-service-properties) or [Azure Data Lake Storage Gen2 linked service](connector-azure-data-lake-storage.md#linked-service-properties) with **Shared access signature, anonymous or account key authentication** that refers to the Azure storage account as the interim storage.
 
 >[!IMPORTANT]
 >- When you use managed identity authentication for your staging linked service, learn the needed configurations for [Azure Blob](connector-azure-blob-storage.md#managed-identity) and [Azure Data Lake Storage Gen2](connector-azure-data-lake-storage.md#managed-identity) respectively.

articles/virtual-network/virtual-network-encryption-overview.md

@@ -51,7 +51,7 @@ Azure Virtual Network encryption has the following limitations:
 
 - In scenarios where a PaaS is involved, the virtual machine where the PaaS is hosted dictates if virtual network encryption is supported. The virtual machine must meet the listed requirements. 
 
-- For Internal load balancer, all virtual machines behind the load balancer must be a supported virtual machine SKU.
+- For Internal load balancer, all virtual machines behind the load balancer must be on a supported virtual machine SKU.
 
 - **AllowUnencrypted** is the only supported enforcement at general availability. **DropUnencrypted** enforcement will be supported in the future.