Merge pull request #228216 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)

Author: huypub

articles/api-management/api-management-howto-use-azure-monitor.md

@@ -141,6 +141,9 @@ To configure resource logs:
 
 1. After configuring details for the log destination or destinations, select **Save**. 
 
+> [!NOTE]
+> Adding a diagnostic setting object might result in a failure if the [MinApiVersion property](/dotnet/api/microsoft.azure.management.apimanagement.models.apiversionconstraint.minapiversion) of your API Management service is set to any API version higher than 2019-12-01. 
+
 For more information, see [Create diagnostic settings to send platform logs and metrics to different destinations](../azure-monitor/essentials/diagnostic-settings.md).
 
 ## View diagnostic data in Azure Monitor

articles/cost-management-billing/cost-management-billing-faq.yml

@@ -21,6 +21,9 @@ sections:
       - question: How do I pay my bill?
         answer: |
           See [Resolve past due balance for your Azure subscription](manage/resolve-past-due-balance.md).
+      - question: How long does it take for my payment to be posted?
+        answer: |
+          See [Check or wire transfer payment processing time](manage/pay-by-invoice.md#check-or-wire-transfer-payment-processing-time).
       - question: How do I find my invoice?
         answer: |
           See [View and download your Microsoft Azure invoice](understand/download-azure-invoice.md).

articles/dms/known-issues-azure-sql-migration-azure-data-studio.md

@@ -225,6 +225,11 @@ WHERE STEP in (3,4,6);
 
 - **Recommendation**: Make sure the target database schema was created before starting the migration. For more information on how to deploy the target database schema, see [SQL Database Projects extension](/sql/azure-data-studio/extensions/sql-database-project-extension)
 
+- **Message**: DatabaseSizeMoreThanMax: `The source database size <Source Database Size> exceeds the maximum allowed size of the target database <Target Database Size>. Check if the target database has enough space.`
+
+- **Cause**: The target database doesn't have enough space.
+
+- **Recommendation**: Make sure the target database schema was created before starting the migration. For more information on how to deploy the target database schema, see [SQL Database Projects extension](/sql/azure-data-studio/extensions/sql-database-project-extension).
 
 - **Message**: NoTablesFound: `Some of the source tables don't exist in the target database. Missing tables: <TableList>`.
 
@@ -269,4 +274,4 @@ Migrating to SQL Server on Azure VMs by using the Azure SQL extension for Azure
 
 - For an overview and installation of the Azure SQL migration extension, see [Azure SQL migration extension for Azure Data Studio](/sql/azure-data-studio/extensions/azure-sql-migration-extension)
 - For more information on known limitations with Log Replay Service,  see [Migrate databases from SQL Server to SQL Managed Instance by using Log Replay Service (Preview)](/azure/azure-sql/managed-instance/log-replay-service-migrate#limitations)
-- For more information on SQL Server on Virtual machine resource limits, see [Checklist: Best practices for SQL Server on Azure VMs](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist)
+- For more information on SQL Server on Virtual machine resource limits, see [Checklist: Best practices for SQL Server on Azure VMs](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist)

articles/external-attack-surface-management/deploying-the-defender-easm-azure-resource.md

@@ -49,6 +49,7 @@ Before you create a Defender EASM resource group, we recommend that you are fami
       -  swedencentral
       -  eastasia
       -  japaneast
+      -  westeurope
 
     ![Screenshot of create resource group basics tab](media/QuickStart-3.png)
 

articles/machine-learning/concept-responsible-ai-dashboard.md

@@ -170,6 +170,7 @@ The following people can use the Responsible AI dashboard, and its corresponding
 - The dataset inputs to the Responsible AI dashboard must be pandas DataFrames in Parquet format. NumPy and SciPy sparse data is currently not supported. 
 - The Responsible AI dashboard currently supports numeric or categorical features. For categorical features, the user has to explicitly specify the feature names.  
 - The Responsible AI dashboard currently doesn't support datasets with more than 10K columns.
+- The Responsible AI dashboard currently doesn't support AutoML MLFlow model.
 
 
 ## Next steps