From f79ca81db7e8f85774ddaf94b64fa673354fcc93 Mon Sep 17 00:00:00 2001 From: Hiroshi Yoshioka <40815708+hyoshioka0128@users.noreply.github.com> Date: Sat, 30 Nov 2024 01:12:59 +0900 Subject: [PATCH 1/6] =?UTF-8?q?Update=20how-to-maintenance-portal.md=20(Ty?= =?UTF-8?q?po=20"flexible=20server"=E2=86=92"Flexible=20Server")?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/mysql/flexible-server/how-to-maintenance-portal.md #PingMSFTDocs --- .../mysql/flexible-server/how-to-maintenance-portal.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/articles/mysql/flexible-server/how-to-maintenance-portal.md b/articles/mysql/flexible-server/how-to-maintenance-portal.md index 1b0175d41d..34da29f4c4 100644 --- a/articles/mysql/flexible-server/how-to-maintenance-portal.md +++ b/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) From 7cd0a0e55297b0becf14c50711da8bb2d741a25e Mon Sep 17 00:00:00 2001 From: Mahdi Azarboon <21277296+azarboon@users.noreply.github.com> Date: Sat, 30 Nov 2024 14:17:24 +0800 Subject: [PATCH 2/6] Update faq.yml --- articles/cosmos-db/faq.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/articles/cosmos-db/faq.yml b/articles/cosmos-db/faq.yml index 6c32c6b011..20d482c881 100644 --- a/articles/cosmos-db/faq.yml +++ b/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: | From dfdcfe1e66717466cc55920729b6a304fcddfa2c Mon Sep 17 00:00:00 2001 From: Hiroshi Yoshioka <40815708+hyoshioka0128@users.noreply.github.com> Date: Sun, 1 Dec 2024 01:00:19 +0900 Subject: [PATCH 3/6] =?UTF-8?q?Update=20how-to-trigger-on-demand-backup.md?= =?UTF-8?q?=20(Typo=20"flexible=20server"=E2=86=92"Flexible=20Server")?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/mysql/flexible-server/how-to-trigger-on-demand-backup.md #PingMSFTDocs --- .../mysql/flexible-server/how-to-trigger-on-demand-backup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/mysql/flexible-server/how-to-trigger-on-demand-backup.md b/articles/mysql/flexible-server/how-to-trigger-on-demand-backup.md index d27906ff4f..3b112de092 100644 --- a/articles/mysql/flexible-server/how-to-trigger-on-demand-backup.md +++ b/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. From a607ce7e965eb764d1b7396580508b40ade2d665 Mon Sep 17 00:00:00 2001 From: Hiroshi Yoshioka <40815708+hyoshioka0128@users.noreply.github.com> Date: Mon, 2 Dec 2024 00:13:41 +0900 Subject: [PATCH 4/6] =?UTF-8?q?Update=20how-to-troubleshoot-cli-errors.md?= =?UTF-8?q?=20(Typo=20"flexible=20server"=E2=86=92"Flexible=20Server")?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/mysql/flexible-server/how-to-troubleshoot-cli-errors.md #PingMSFTDocs --- .../how-to-troubleshoot-cli-errors.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/articles/mysql/flexible-server/how-to-troubleshoot-cli-errors.md b/articles/mysql/flexible-server/how-to-troubleshoot-cli-errors.md index 3d6e4f8767..5a58c0422d 100644 --- a/articles/mysql/flexible-server/how-to-troubleshoot-cli-errors.md +++ b/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,10 +29,10 @@ 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 \ @@ -40,7 +40,7 @@ Currently, Azure CLI doesn't support turning on debug logging, but you can retri --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 `. 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).
- 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).
- 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.| From c864f6636ecf4555cdfe2cb65559f17236ec17f7 Mon Sep 17 00:00:00 2001 From: kabharati <92822591+kabharati@users.noreply.github.com> Date: Mon, 2 Dec 2024 08:56:21 -0500 Subject: [PATCH 5/6] Update concepts-backup-restore.md Added preview tag for LTR --- articles/postgresql/flexible-server/concepts-backup-restore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/postgresql/flexible-server/concepts-backup-restore.md b/articles/postgresql/flexible-server/concepts-backup-restore.md index 38865211cf..d745dcbc48 100644 --- a/articles/postgresql/flexible-server/concepts-backup-restore.md +++ b/articles/postgresql/flexible-server/concepts-backup-restore.md @@ -192,7 +192,7 @@ On-demand backup feature is currently not supported with the Burstable server co We are aware of an existing bug that allows taking on-demand backups on Replicas, even though Point-in-Time Restore (PITR) is not supported in this context. This issue will be addressed to ensure that on-demand backups can only be performed on the Primary server. -## Long-term retention +## Long-term retention (preview) Azure Backup and Azure Database for PostgreSQL flexible server services have built an enterprise-class long-term backup solution for Azure Database for PostgreSQL flexible server instances that retains backups for up to 10 years. You can use long-term retention (LTR) independently or in addition to the automated backup solution offered by Azure Database for PostgreSQL flexible server, which offers retention of up to 35 days. Automated backups are physical backups suited for operational recoveries, especially when you want to restore from the latest backups. Long-term backups help you with your compliance needs, are more granular, and are taken as logical backups using native pg_dump. In addition to long-term retention, the solution offers the following capabilities: From ad21b9940c2487f4a8945156ebb86bde5d6aacea Mon Sep 17 00:00:00 2001 From: Hiroshi Yoshioka <40815708+hyoshioka0128@users.noreply.github.com> Date: Tue, 3 Dec 2024 01:25:02 +0900 Subject: [PATCH 6/6] =?UTF-8?q?Update=20concepts-audit-logs.md=20(Typo=20"?= =?UTF-8?q?flexible=20server"=E2=86=92"Flexible=20Server")?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/mysql/flexible-server/concepts-audit-logs.md #PingMSFTDocs --- articles/mysql/flexible-server/concepts-audit-logs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/mysql/flexible-server/concepts-audit-logs.md b/articles/mysql/flexible-server/concepts-audit-logs.md index ee2ee74ed1..99da8078d2 100644 --- a/articles/mysql/flexible-server/concepts-audit-logs.md +++ b/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