[MySQL] changed 6 files flexible server names

Author: markingmyname

articles/mysql/flexible-server/azure-pipelines-deploy-database-task.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Pipelines task for Azure Database for MySQL - Flexible Server
-description: Enable Azure Database for MySQL - Flexible Server CLI task for using with Azure Pipelines
+title: Azure Pipelines task for Azure Database for MySQL - Flexible Server 
+description: Enable Azure Database for MySQL - Flexible Server CLI task for using with Azure Pipelines.
 ms.service: mysql
 ms.subservice: flexible-server
 ms.topic: how-to
@@ -12,7 +12,7 @@ ms.date: 08/09/2021
 
 # Azure Pipelines for Azure Database for MySQL - Flexible Server
 
-You can automatically deploy your database updates to Azure Database for MySQL - Flexible Server after every successful build with **Azure Pipelines**.  You can use Azure CLI task to update the database either with a SQL file or an inline SQL script against the database. This task  can be run on cross-platform agents running on Linux, macOS, or Windows operating systems.
+You can automatically deploy your database updates to an Azure Database for MySQL flexible server after every successful build with **Azure Pipelines**. You can use Azure CLI task to update the database either with a SQL file or an inline SQL script against the database. This task  can be run on cross-platform agents running on Linux, macOS, or Windows operating systems.
 
 ## Prerequisites
 
@@ -22,8 +22,8 @@ You can automatically deploy your database updates to Azure Database for MySQL -
 - Microsoft hosted agents have Azure CLI pre-installed. However if you are using private agents, [install Azure CLI](/cli/azure/install-azure-cli) on the computer(s) that run the build and release agent. If an agent is already running on the machine on which the Azure CLI is installed, restart the agent to ensure all the relevant stage variables are updated.
 
 This quickstart uses the resources created in either of these guides as a starting point:
-- Create an Azure Database for MySQL - Flexible Server using [Azure portal](./quickstart-create-server-portal.md) or  [Azure CLI](./quickstart-create-server-cli.md)
 
+- Create an Azure Database for MySQL flexible server using [Azure portal](./quickstart-create-server-portal.md) or [Azure CLI](./quickstart-create-server-cli.md)
 
 ## Use SQL file
 

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

@@ -7,7 +7,7 @@ ms.reviewer:
 ms.date: 11/21/2022
 ms.service: mysql
 ms.subservice: flexible-server
-ms.topic: conceptual
+ms.topic: conceptual 
 ---
 
 # Track database activity with Audit Logs in Azure Database for MySQL - Flexible Server
@@ -46,7 +46,7 @@ Other parameters you can adjust to control audit logging behavior include:
 
 ## Access audit logs
 
-Audit logs are integrated with Azure Monitor diagnostic settings. Once you've enabled audit logs on your MySQL flexible server, you can emit them to Azure Monitor logs, Event Hubs, or Azure Storage. To learn more about diagnostic settings, see the [diagnostic logs documentation](../../azure-monitor/essentials/platform-logs-overview.md). To learn more about how to enable diagnostic settings in the Azure portal, see the [audit log portal article](tutorial-configure-audit.md#set-up-diagnostics).
+Audit logs are integrated with Azure Monitor diagnostic settings. Once you've enabled audit logs on your flexible server, you can emit them to Azure Monitor logs, Event Hubs, or Azure Storage. To learn more about diagnostic settings, see the [diagnostic logs documentation](../../azure-monitor/essentials/platform-logs-overview.md). To learn more about how to enable diagnostic settings in the Azure portal, see the [audit log portal article](tutorial-configure-audit.md#set-up-diagnostics).
 
 > [!NOTE]  
 > Premium Storage accounts are not supported if you send the logs to Azure storage via diagnostics and settings.
@@ -198,4 +198,3 @@ Once your audit logs are piped to Azure Monitor Logs through Diagnostic Logs, yo
 
 - Learn more about [slow query logs](concepts-slow-query-logs.md)
 - Configure [auditing](tutorial-query-performance-insights.md)
-<!-- - [How to configure audit logs in the Azure portal](howto-configure-audit-logs-portal.md)-->

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

@@ -1,6 +1,6 @@
 ---
 title: Active Directory authentication - Azure Database for MySQL - Flexible Server
-description: Learn about the concepts of Azure Active Directory for authentication with Azure Database for MySQL - Flexible Server
+description: Learn about the concepts of Azure Active Directory for authentication with Azure Database for MySQL - Flexible Server.
 author: vivgk
 ms.author: vivgk
 ms.reviewer: maghan
@@ -10,7 +10,7 @@ ms.subservice: flexible-server
 ms.topic: conceptual
 ---
 
-# Active Directory authentication - Azure Database for MySQL - Flexible Server
+# Active Directory authentication for Azure Database for MySQL - Flexible Server
 
 [!INCLUDE[applies-to-mysql-flexible-server](../includes/applies-to-mysql-flexible-server.md)]
 
@@ -23,17 +23,17 @@ Microsoft Azure Active Directory (Azure AD) authentication is a mechanism of con
 - Multiple forms of authentication supported by Azure Active Directory, which can eliminate the need to store passwords
 - Customers can manage database permissions using external (Azure AD) groups.
 - Azure AD authentication uses MySQL database users to authenticate identities at the database level
-- Support of token-based authentication for applications connecting to Azure Database for MySQL - Flexible Server
+- Support of token-based authentication for applications connecting to Azure Database for MySQL flexible server
 
 ## Use the steps below to configure and use Azure AD authentication
 
-1. Select your preferred authentication method for accessing the MySQL flexible server. By default, the authentication selected is set to MySQL authentication only. Select Azure Active Directory authentication only or MySQL and Azure Active Directory authentication to enable Azure AD authentication.
+1. Select your preferred authentication method for accessing the flexible server. By default, the authentication selected is set to MySQL authentication only. Select Azure Active Directory authentication only or MySQL and Azure Active Directory authentication to enable Azure AD authentication.
 1. Select the user managed identity (UMI) with the following privileges to configure Azure AD authentication:
     - [User.Read.All](/graph/permissions-reference#user-permissions): Allows access to Azure AD user information.
     - [GroupMember.Read.All](/graph/permissions-reference#group-permissions): Allows access to Azure AD group information.
     - [Application.Read.ALL](/graph/permissions-reference#application-resource-permissions): Allows access to Azure AD service principal (application) information.
 
-1. Add Azure AD Admin. It can be Azure AD Users or Groups, which have access to Azure Database for MySQL - Flexible Server.
+1. Add Azure AD Admin. It can be Azure AD Users or Groups, which has access to a flexible server.
 1. Create database users in your database mapped to Azure AD identities.
 1. Connect to your database by retrieving a token for an Azure AD identity and logging in.
 
@@ -44,27 +44,27 @@ Microsoft Azure Active Directory (Azure AD) authentication is a mechanism of con
 
 User-managed identities are required for Azure Active Directory authentication. When a User-Assigned Identity is linked to the flexible server, the Managed Identity Resource Provider (MSRP) issues a certificate internally to that identity. When the managed identity is deleted, the corresponding service principal is automatically removed.
 
-The service then uses the managed identity to request access tokens for services that support Azure AD authentication. Azure Database currently supports only a User-assigned Managed Identity (UMI) for MySQL-Flexible Server. For more information, see [Managed identity types](../../active-directory/managed-identities-azure-resources/overview.md#managed-identity-types) in Azure.
+The service then uses the managed identity to request access tokens for services that support Azure AD authentication. Azure Database currently supports only a User-assigned Managed Identity (UMI) for Azure Database for MySQL - Flexible Server. For more information, see [Managed identity types](../../active-directory/managed-identities-azure-resources/overview.md#managed-identity-types) in Azure.
 
 The following high-level diagram summarizes how authentication works using Azure AD authentication with Azure Database for MySQL. The arrows indicate communication pathways.
 
 :::image type="content" source="media/concepts-azure-ad-authentication/azure-ad-authentication-flow.jpg" alt-text="Diagram of how Azure AD authentication works.":::
 
 1. Your application can request a token from the Azure Instance Metadata Service identity endpoint.
 1. When you use the client ID and certificate, a call is made to Azure AD to request an access token.
-1. A JSON Web Token (JWT) access token is returned by Azure AD. Your application sends the access token on a call to Azure Database for MySQL - Flexible Server.
-1. MySQL flexible server validates the token with Azure AD.
+1. A JSON Web Token (JWT) access token is returned by Azure AD. Your application sends the access token on a call to your flexible server.
+1. The flexible server validates the token with Azure AD.
 
 ## Administrator structure
 
 There are two Administrator accounts for the MySQL server when using Azure AD authentication: the original MySQL administrator and the Azure AD administrator.
 
-Only the administrator based on an Azure AD account can create the first Azure AD contained database user in a user database. The Azure AD administrator sign-in can be an Azure AD user or an Azure AD group. When the administrator is a group account, it can be used by any group member, enabling multiple Azure AD administrators for the MySQL flexible server. Using a group account as an administrator enhances manageability by allowing you to centrally add and remove group members in Azure AD without changing the users or permissions in the MySQL Flexible server. Only one Azure AD administrator (a user or group) can be configured at a time.
+Only the administrator based on an Azure AD account can create the first Azure AD contained database user in a user database. The Azure AD administrator sign-in can be an Azure AD user or an Azure AD group. When the administrator is a group account, it can be used by any group member, enabling multiple Azure AD administrators for the flexible server. Using a group account as an administrator enhances manageability by allowing you to centrally add and remove group members in Azure AD without changing the users or permissions in the Flexible server. Only one Azure AD administrator (a user or group) can be configured at a time.
 
 :::image type="content" source="media/concepts-azure-ad-authentication/azure-ad-admin-structure.jpg" alt-text="Diagram of Azure AD admin structure.":::
 
-Methods of authentication for accessing the MySQL flexible server include:  
-- MySQL Authentication only - This is the default option. Only the native MySQL Authentication with a MySQL sign-in and password can be used to access Azure Database for MySQL - Flexible Server.
+Methods of authentication for accessing the flexible server include:  
+- MySQL authentication only - This is the default option. Only the native MySQL authentication with a MySQL sign-in and password can be used to access the flexible server.
 - Only Azure AD authentication - MySQL native authentication is disabled, and users are able to authenticate using only their Azure AD user and token. To enable this mode, the server parameter **aad_auth_only** is set to _enabled_.
 - Authentication with MySQL and Azure AD - Both native MySQL authentication and Azure AD authentication are supported. To enable this mode, the server parameter **aad_auth_only** is set to _disabled_.
 
@@ -90,7 +90,7 @@ Azure AD authentication in Azure Database for MySQL - Flexible Server ensures th
 - Token is signed by Azure AD and hasn't been tampered.
 - Token was issued by Azure AD for the tenant associated with the server.
 - Token hasn't expired.
-- Token is for the Azure Database for MySQL - Flexible Server resource (and not another Azure resource).
+- Token is for the flexible server resource (and not another Azure resource).
 
 ## Connect using Azure AD identities
 
@@ -112,9 +112,9 @@ Once you authenticate against the Active Directory, you retrieve a token. This t
 
 ## Other considerations
 
-- Only one Azure AD administrator can be configured for an Azure Database for MySQL - Flexible Server at any time.
+- You can only configure one Azure AD administrator per flexible server at any time.
 
-- Only an Azure AD administrator for MySQL can initially connect to the Azure Database for MySQL - Flexible Server using an Azure Active Directory account. The Active Directory administrator can configure subsequent Azure AD database users or an Azure AD group. When the administrator is a group account, it can be used by any group member, enabling multiple Azure AD administrators for the MySQL Flexible server. Using a group account as an administrator enhances manageability by allowing you to centrally add and remove group members in Azure AD without changing the users or permissions in the MySQL Flexible server.
+- Only an Azure AD administrator for MySQL can initially connect to the flexible server using an Azure Active Directory account. The Active Directory administrator can configure subsequent Azure AD database users or an Azure AD group. When the administrator is a group account, it can be used by any group member, enabling multiple Azure AD administrators for the flexible server. Using a group account as an administrator enhances manageability by allowing you to centrally add and remove group members in Azure AD without changing the users or permissions in the flexible server.
 
 - If a user is deleted from Azure AD, that user can no longer authenticate with Azure AD. Therefore, acquiring an access token for that user is no longer possible. Although the matching user is still in the database, connecting to the server with that user isn't possible.
 
@@ -123,10 +123,10 @@ Once you authenticate against the Active Directory, you retrieve a token. This t
 
 - If the Azure AD admin is removed from the server, the server is no longer associated with an Azure AD tenant, and therefore all Azure AD logins are disabled for the server. Adding a new Azure AD admin from the same tenant re-enables Azure AD logins.
 
-- Azure Database for MySQL - Flexible Server matches access tokens to the Azure Database for MySQL users using the user's unique Azure AD user ID instead of the username. This means that if an Azure AD user is deleted in Azure AD and a new user is created with the same name, Azure Database for MySQL considers that a different user. Therefore, if a user is deleted from Azure AD and then a new user with the same name is added, the new user isn't able to connect with the existing user.
+- A flexible server matches access tokens to the Azure Database for MySQL users using the user's unique Azure AD user ID instead of the username. This means that if an Azure AD user is deleted in Azure AD and a new user is created with the same name, the flexible server considers that a different user. Therefore, if a user is deleted from Azure AD and then a new user with the same name is added, the new user isn't able to connect with the existing user.
 
 > [!NOTE]  
-> The subscriptions of an Azure MySQL flexible server with Azure AD authentication enabled cannot be transferred to another tenant or directory.
+> The subscriptions of a flexible server with Azure AD authentication enabled can't be transferred to another tenant or directory.
 
 ## Next steps