Merge pull request #937 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-databases-docs (branch main)

articles/cosmos-db/faq.yml

@@ -47,6 +47,10 @@ sections:
           Can I use multiple APIs to access my data?
         answer: |
           Azure Cosmos DB is Microsoft's globally distributed, multi-model database service. Multi-model refers to Azure Cosmos DB's support for multiple APIs and data models. In this paradigm, different APIs use different data formats for storage and wire protocol. For example; NoSQL uses JSON, MongoDB uses binary-encoded JSON (BSON), Table uses Entity Data Model (EDM), Cassandra uses Cassandra Query Language (CQL), Gremlin uses JSON format. As a result, we recommend using the same API for all access to the data in a given account.
+      - question: |
+          Can I integrate Azure Cosmos DB directly with other services?
+        answer: |
+          Yes. Azure Cosmos DB APIs allow direct integration. For example, the Azure Cosmos DB REST APIs can be integrated with Azure API Management for CRUD operations, eliminating the need for intermediate services like Azure Functions.        
       - question: |
           Is Azure Cosmos DB HIPAA compliant?
         answer: |

articles/mysql/flexible-server/concepts-audit-logs.md

@@ -14,7 +14,7 @@ ms.topic: conceptual
 
 [!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
-Azure Database for MySQL flexible server provides users with the ability to configure audit logs. Audit logs can be used to track database-level activity including connection, admin, DDL, and DML events. These types of logs are commonly used for compliance purposes.
+Azure Database for MySQL Flexible Server provides users with the ability to configure audit logs. Audit logs can be used to track database-level activity including connection, admin, DDL, and DML events. These types of logs are commonly used for compliance purposes.
 
 ## Configure audit logging
 
@@ -198,7 +198,7 @@ Once your audit logs are piped to Azure Monitor Logs through Diagnostic Logs, yo
     | render timechart
     ```
 
-- List audited events across all Azure Database for MySQL flexible server instances with Diagnostic Logs enabled for audit logs
+- List audited events across all Azure Database for MySQL Flexible Server instances with Diagnostic Logs enabled for audit logs
 
     ```kusto
     AzureDiagnostics

articles/mysql/flexible-server/how-to-maintenance-portal.md

@@ -15,17 +15,17 @@ ms.topic: how-to
 [!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
 
-You can specify maintenance options for each Azure Database for MySQL flexible server instance in your Azure subscription. Options include the maintenance schedule and notification settings for upcoming and finished maintenance events.
+You can specify maintenance options for each Azure Database for MySQL Flexible Server instance in your Azure subscription. Options include the maintenance schedule and notification settings for upcoming and finished maintenance events.
 
 ## Prerequisites
 
 To complete this how-to guide, you need:
 
-- An [Azure Database for MySQL flexible server instance](quickstart-create-server-portal.md)
+- An [Azure Database for MySQL Flexible Server instance](quickstart-create-server-portal.md)
 
 ## Specify maintenance schedule options
 
-1. On the Azure Database for MySQL flexible server page, under the **Settings** heading, choose **Maintenance** to open scheduled maintenance options.
+1. On the Azure Database for MySQL Flexible Server page, under the **Settings** heading, choose **Maintenance** to open scheduled maintenance options.
 2. The default (system-managed) schedule is a random day of the week, and 60-minute window for maintenance start between 11pm and 7am local server time. If you want to customize this schedule, choose **Custom schedule**. You can then select a preferred day of the week, and a 60-minute window for maintenance start time.
 
 ## Reschedule Maintenance
@@ -54,9 +54,9 @@ There's no limitation on how many times a maintenance can be rescheduled, as lon
 
 ## Notifications about scheduled maintenance events
 
-You can use Azure Service Health to [view notifications](/azure/service-health/service-notifications) about upcoming and performed scheduled maintenance on your Azure Database for MySQL flexible server instance. You can also [set up](/azure/service-health/resource-health-alert-monitor-guide) alerts in Azure Service Health to get notifications about maintenance events.
+You can use Azure Service Health to [view notifications](/azure/service-health/service-notifications) about upcoming and performed scheduled maintenance on your Azure Database for MySQL Flexible Server instance. You can also [set up](/azure/service-health/resource-health-alert-monitor-guide) alerts in Azure Service Health to get notifications about maintenance events.
 
 ## Next steps
 
-* Learn about [scheduled maintenance in Azure Database for MySQL flexible server](concepts-maintenance.md)
+* Learn about [scheduled maintenance in Azure Database for MySQL Flexible Server](concepts-maintenance.md)
 * Lean about [Azure Service Health](/azure/service-health/overview)

articles/mysql/flexible-server/how-to-trigger-on-demand-backup.md

@@ -19,7 +19,7 @@ This article provides a step-by-step procedure to trigger an on-demand backup fr
 
 ## Prerequisites
 
-You need an Azure Database for MySQL flexible server instance to complete this how-to guide.
+You need an Azure Database for MySQL Flexible Server instance to complete this how-to guide.
 
 - Create a MySQL flexible server instance by following the steps in the article [Quickstart: Create an instance of Azure Database for MySQL - Flexible Server by using the Azure portal](quickstart-create-server-portal.md).
 
@@ -45,7 +45,7 @@ Follow these steps to trigger backup on demand:
 
 Follow these steps to trigger an on-demand backup and export:
 
-1. In the [Azure portal](https://portal.azure.com/), choose your Azure Database for MySQL flexible server instance to take a backup of and export.
+1. In the [Azure portal](https://portal.azure.com/), choose your Azure Database for MySQL Flexible Server instance to take a backup of and export.
 
 1. Under **Settings** select **Backup and restore** from the left panel.
 

articles/mysql/flexible-server/how-to-troubleshoot-cli-errors.md

@@ -17,7 +17,7 @@ ms.custom:
 
 [!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
-This article helps you troubleshoot common issues with Azure CLI when using Azure Database for MySQL flexible server.
+This article helps you troubleshoot common issues with Azure CLI when using Azure Database for MySQL Flexible Server.
 
 ## Command not found
 
@@ -29,18 +29,18 @@ Currently, Azure CLI doesn't support turning on debug logging, but you can retri
 
 >[!NOTE]
 >
-> - Replace `examplegroup` and `exampledeployment` with the correct resource group and deployment name for your Azure Database for MySQL flexible server instance.
+> - Replace `examplegroup` and `exampledeployment` with the correct resource group and deployment name for your Azure Database for MySQL Flexible Server instance.
 > - You can see the Deployment name in the deployments page in your resource group. See [how to find the deployment name](/azure/azure-resource-manager/templates/deployment-history?tabs=azure-portal).
 
-1. List the deployments in resource group to identify the Azure Database for MySQL flexible server deployment.
+1. List the deployments in resource group to identify the Azure Database for MySQL Flexible Server deployment.
 
     ```azurecli
     az deployment operation group list \
       --resource-group examplegroup \
       --name exampledeployment
     ```
 
-2. Get the request content of the Azure Database for MySQL flexible server deployment.
+2. Get the request content of the Azure Database for MySQL Flexible Server deployment.
 
     ```azurecli
     az deployment operation group list \
@@ -65,15 +65,15 @@ Currently, Azure CLI doesn't support turning on debug logging, but you can retri
 |MissingSubscriptionRegistration|Register your subscription with the resource provider. Run the command `az provider register --namespace Microsoft.DBMySQL` to resolve the issue.|
 |InternalServerError| Try to view the activity logs for your server to see if there's more information. Run the command `az monitor activity-log list --correlation-id <enter correlation-id>`. You can try the same CLI command after a few minutes. If the issue persists, [report it](https://github.com/Azure/azure-cli/issues) or reach out to Microsoft support.|
 |ResourceNotFound| Resource being referenced can't be found.  You can check resource properties, or check if the resource is deleted or in another subscription. |
-|LocationNotAvailableForResourceType| - Check availability of Azure Database for MySQL flexible server in [Azure regions](https://azure.microsoft.com/global-infrastructure/services/?products=mysql). <br>- Check if the Azure Database for MySQL flexible server instance Resource types is registered with your subscription. |
+|LocationNotAvailableForResourceType| - Check availability of Azure Database for MySQL Flexible Server in [Azure regions](https://azure.microsoft.com/global-infrastructure/services/?products=mysql). <br>- Check if the Azure Database for MySQL Flexible Server instance Resource types is registered with your subscription. |
 |ResourceGroupBeingDeleted| Resource group is being deleted. Wait for deletion to complete.|
 |PasswordTooLong| The provided password is too long. It must contain between 8 and 128 characters. Your password must contain characters from three of the following categories: English uppercase letters, English lowercase letters, numbers (0 through 9), and nonalphanumeric characters (!, $, #, %, etc.).|
 |PasswordNotComplex| The provided password isn't complex enough.  It must contain between 8 and 128 characters. Your password must contain characters from three of the following categories: English uppercase letters, English lowercase letters, numbers (0 through 9), and nonalphanumeric characters (!, $, #, %, etc.).|
 |PasswordTooShort| It must contain between 8 and 128 characters. Your password must contain characters from three of the following categories: English uppercase letters, English lowercase letters, numbers (0 through 9), and nonalphanumeric characters (!, $, #, %, etc.).|
 |SubscriptionNotFound| The requested subscription wasn't found. Run `az account list all` to see all your current subscriptions.|
 |InvalidParameterValue| An invalid value was given to a parameter. Check the [CLI reference docs](/cli/azure/mysql/flexible-server) to see the correct values supported for the arguments.|
-|InvalidLocation| An invalid location was specified. Check availability of Azure Database for MySQL flexible server in [Azure regions](https://azure.microsoft.com/global-infrastructure/services/?products=mysql) |
-|InvalidServerName| Identified an invalid server name. Check the server name. Run the command [az mysql flexible-server list](/cli/azure/mysql/flexible-server#az-mysql-flexible-server-list) to see all list of Azure Database for MySQL flexible server instances available. |
+|InvalidLocation| An invalid location was specified. Check availability of Azure Database for MySQL Flexible Server in [Azure regions](https://azure.microsoft.com/global-infrastructure/services/?products=mysql) |
+|InvalidServerName| Identified an invalid server name. Check the server name. Run the command [az mysql flexible-server list](/cli/azure/mysql/flexible-server#az-mysql-flexible-server-list) to see all list of Azure Database for MySQL Flexible Server instances available. |
 |InvalidResourceIdSegment| A syntax error was identified in your Azure Resource Manager template. Use a JSON formatter tool to validate the JSON to identify the syntax error.|
 |InvalidUserName| Enter a valid username. The admin user name can't be azure_superuser, azure_pg_admin, admin, administrator, root, guest, or public. It can't start with pg_.|
 |BlockedUserName| The admin user name can't be azure_superuser, azure_pg_admin, admin, administrator, root, guest, or public. It can't start with pg_. Avoid using these patterns in the admin name.|