Merge pull request #275964 from markingmyname/securitymysql

Jill Grant · web-flow · commit ed85199e05a5 · 2024-05-21T17:29:57.000-06:00
[Security effort] REMOVED email due to Security effort (Bulk edit)
diff --git a/articles/mysql/concepts-version-policy.md b/articles/mysql/concepts-version-policy.md
@@ -107,7 +107,7 @@ A: Some compatibility issues may arise due to changes in MySQL v8.0. It's import
 
 __Q: What support is available if I encounter issues during the upgrade process?__
 
-A: If you have questions, get answers from community experts in [Microsoft Q&A](https://aka.ms/microsoft-azure-mysql-qa). If you have a support plan and you need technical help, create a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest). You can also email the [Azure Database for MySQL product team](mailto:AskAzureDBforMySQL@service.microsoft.com).
+A: If you have questions, get answers from community experts in [Microsoft Q&A](https://aka.ms/microsoft-azure-mysql-qa). If you have a support plan and you need technical help, create a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
 
 __Q: What will happen to my data during the upgrade?__
 
diff --git a/articles/mysql/flexible-server/how-to-troubleshoot-common-errors.md b/articles/mysql/flexible-server/how-to-troubleshoot-common-errors.md
@@ -132,6 +132,5 @@ The above error occurs if:
 If you didn't find the answer you're looking for, consider the following options:
 
 * Post your question on [Microsoft Q&A question page](/answers/topics/azure-database-mysql.html) or [Stack Overflow](https://stackoverflow.com/questions/tagged/azure-database-mysql).
-* Send an email to the Azure Database for MySQL flexible server team [@Ask Azure DB for MySQL](mailto:AskAzureDBforMySQL@service.microsoft.com). This email address isn't a technical support alias.
 * Contact Azure Support, [file a ticket from the Azure portal](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade). To fix an issue with your account, file a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) in the Azure portal.
 * To provide feedback or to request new features, create an entry via [UserVoice](https://feedback.azure.com/d365community/forum/47b1e71d-ee24-ec11-b6e6-000d3a4f0da0).
diff --git a/articles/mysql/flexible-server/overview-single.md b/articles/mysql/flexible-server/overview-single.md
@@ -60,10 +60,9 @@ Azure Database for MySQL single server is a fully managed database service desig
 
 Single servers are best suited **only for existing applications already leveraging single server**. For all new developments or migrations, Azure Database for MySQL flexible server would be the recommended deployment option. To learn about the differences between flexible server and single server deployment options, refer to [select the right deployment option](../select-right-deployment-type.md).
 
-## Contacts
-For any questions or suggestions you might have about working with Azure Database for MySQL flexible server, send an email to the Azure Database for MySQL flexible server team ([@Ask Azure Database for MySQL flexible server](mailto:AskAzureDBforMySQL@service.microsoft.com)). This email address isn't a technical support alias.
+## Feedback and support
 
-In addition, consider the following points of contact as appropriate:
+For any questions or suggestions you might have about working with Azure Database for MySQL flexible server, consider the following points of contact:
 
 - To contact Azure Support, [file a ticket from the Azure portal](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
 - To fix an issue with your account, file a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) in the Azure portal.
diff --git a/articles/mysql/flexible-server/overview.md b/articles/mysql/flexible-server/overview.md
@@ -226,11 +226,9 @@ One advantage of running your workload in Azure is its global reach. Azure Datab
 | West US 2 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 | West US 3 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
 
-## Contacts
+## Feedback and support
 
-For any questions or suggestions you might have on Azure Database for MySQL flexible server, send an email to the Azure Database for MySQL flexible server team ([@Ask Azure Database for MySQL flexible server](mailto:AskAzureDBforMySQL@service.microsoft.com)). This email address isn't a technical support alias.
-
-In addition, consider the following points of contact as appropriate:
+For any questions or suggestions you might have about working with Azure Database for MySQL flexible server, consider the following points of contact:
 
 - To contact Azure Support, [file a ticket from the Azure portal](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
 - To fix an issue with your account, file a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) in the Azure portal.
diff --git a/articles/mysql/migrate/mysql-on-premises-azure-db/03-assessment.md b/articles/mysql/migrate/mysql-on-premises-azure-db/03-assessment.md
@@ -195,9 +195,6 @@ There are currently three tiers:
 
 The tier decision can be influenced by the RTO and RPO requirements of the data workload. When the data workload requires over 4 TB of storage, an extra step is required. Review and select [a region that supports](../../concepts-pricing-tiers.md#storage) up to 16 TB of storage.
 
-> [!NOTE]
-> Contact the MySQL team (AskAzureDBforMySQL@service.microsoft.com) for regions that don't support your storage requirements.
-
 Typically, the decision-making focuses on the storage and IOPS, or Input/output Operations Per Second, needs. Thus, the target system always needs at least as much storage as in the source system. Additionally, since IOPS are allocated 3/GB, it's important to match up the IOPs needs to the final storage size.
 
 | Factors | Tier |
diff --git a/articles/mysql/migrate/mysql-on-premises-azure-db/14-summary.md b/articles/mysql/migrate/mysql-on-premises-azure-db/14-summary.md
@@ -31,19 +31,14 @@ Application architecture and design can provide strong indicators as to the leve
 
 In the end, several tools exist in the marketplace ranging from free to commercial. This document covered the steps required if the team plans a database migration using one of the more popular open-source tool options. Whichever path that is chosen, Microsoft and the MySQL community have the tools and expertise to make the database migration successful.
 
-## Questions and Feedback
+## Feedback and support
 
-For any questions or suggestions about working with Azure Database for MySQL, send an email to the Azure Database for MySQL Team (AskAzureDBforMySQL@service.microsoft.com). 
+For any questions or suggestions you might have about working with Azure Database for MySQL flexible server, consider the following points of contact:
 
-> [!Important]
-> The Azure Database for MySQL Team address is for general questions only and not for support tickets.
+- To contact Azure Support, [file a ticket from the Azure portal](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
+- To fix an issue with your account, file a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) in the Azure portal.
+- To provide feedback or to request new features, create an entry via [UserVoice](https://feedback.azure.com/d365community/forum/47b1e71d-ee24-ec11-b6e6-000d3a4f0da0).
 
-In addition, consider these points of contact as appropriate:
-
-  - To contact Azure Support or fix an issue with your account, [file a ticket from the Azure portal. ](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview)
-
-  - To provide feedback or to request new features, create an entry via [UserVoice.](https://feedback.azure.com/d365community/forum/47b1e71d-ee24-ec11-b6e6-000d3a4f0da0)
-fwill
 ## Find a partner to help migrate
 
 This guide can be overwhelming, but don’t fret\! There are many experts in the community with a proven migration track record. [Search for a Microsoft Partner](https://www.microsoft.com/solution-providers/home) or [Microsoft MVP](https://mvp.microsoft.com/MvpSearch) to help with finding the most appropriate migration strategy. You aren't alone\!
diff --git a/articles/mysql/single-server/concepts-data-encryption-mysql.md b/articles/mysql/single-server/concepts-data-encryption-mysql.md
@@ -139,7 +139,7 @@ For Azure Database for MySQL, the support for encryption of data at rest using c
 
     > [!NOTE]
     > - All new MySQL servers created in the [Azure regions](concepts-pricing-tiers.md#storage) supporting general purpose storage v2, support for encryption with customer manager keys is **available**. Point In Time Restored (PITR) server or read replica will not qualify though in theory they are ‘new’.
-    > - To validate if your provisioned server general purpose storage v2, you can go to the pricing tier blade in the portal and see the max storage size supported by your provisioned server. If you can move the slider up to 4TB, your server is on general purpose storage v1 and will not support encryption with customer managed keys. However, the data is encrypted using service managed keys at all times. Please reach out to AskAzureDBforMySQL@service.microsoft.com if you have any questions.
+    > - To validate if your provisioned server general purpose storage v2, you can go to the pricing tier blade in the portal and see the max storage size supported by your provisioned server. If you can move the slider up to 4TB, your server is on general purpose storage v1 and will not support encryption with customer managed keys. However, the data is encrypted using service managed keys at all times.
 
 * Encryption is only supported with RSA 2048 cryptographic key.
 
diff --git a/articles/mysql/single-server/concepts-infrastructure-double-encryption.md b/articles/mysql/single-server/concepts-infrastructure-double-encryption.md
@@ -63,8 +63,7 @@ For Azure Database for MySQL, the support for infrastruction double encryption h
 
     > [!NOTE]
     > - All new MySQL servers created in the [Azure regions](concepts-pricing-tiers.md#storage) supporting general purpose storage v2, support for encryption with customer manager keys is **available**. Point In Time Restored (PITR) server or read replica will not qualify though in theory they are ‘new’.
-    > - To validate if your provisioned server general purpose storage v2, you can go to the pricing tier blade in the portal and see the max storage size supported by your provisioned server. If you can move the slider up to 4TB, your server is on general purpose storage v1 and will not support encryption with customer managed keys. However, the data is encrypted using service managed keys at all times. Please reach out to AskAzureDBforMySQL@service.microsoft.com if you have any questions.
-
+    > - To validate if your provisioned server general purpose storage v2, you can go to the pricing tier blade in the portal and see the max storage size supported by your provisioned server. If you can move the slider up to 4TB, your server is on general purpose storage v1 and will not support encryption with customer managed keys. However, the data is encrypted using service managed keys at all times.
 
 
 ## Next steps
diff --git a/articles/mysql/single-server/concepts-planned-maintenance-notification.md b/articles/mysql/single-server/concepts-planned-maintenance-notification.md
@@ -78,7 +78,6 @@ A transient error, also known as a transient fault, is an error that will resolv
 
 ## Next steps
 
-- For any questions or suggestions you might have about working with Azure Database for MySQL, send an email to the Azure Database for MySQL Team at AskAzureDBforMySQL@service.microsoft.com
 - See [How to set up alerts](how-to-alert-on-metric.md) for guidance on creating an alert on a metric.
 - [Troubleshoot connection issues to Azure Database for MySQL - Single Server](how-to-troubleshoot-common-connection-issues.md)
 - [Handle transient errors and connect efficiently to Azure Database for MySQL - Single Server](concepts-connectivity.md)
diff --git a/articles/mysql/single-server/single-server-overview.md b/articles/mysql/single-server/single-server-overview.md
@@ -83,11 +83,9 @@ The service runs community version of MySQL. This allows full application compat
 - **Azure Database Migration Service** – For seamless and simplified offline migrations to single server with high speed data migration, [Azure Database Migration Service](../../dms/tutorial-mysql-azure-mysql-offline-portal.md) can be leveraged. 
 - **Data-in replication** – For minimal downtime migrations, data-in replication, which relies on binlog based replication can also be leveraged. Data-in replication is preferred for minimal downtime migrations by hands-on experts looking for more control over migration. See [data-in replication](concepts-data-in-replication.md) for details.
 
-## Contacts
+## Feedback and support
 
-For any questions or suggestions you might have about working with Azure Database for MySQL, send an email to the Azure Database for MySQL Team ([@Ask Azure DB for MySQL](mailto:AskAzureDBforMySQL@service.microsoft.com)). This email address isn't a technical support alias.
-
-In addition, consider the following points of contact as appropriate:
+For any questions or suggestions you might have about working with Azure Database for MySQL flexible server, consider the following points of contact:
 
 - To contact Azure Support, [file a ticket from the Azure portal](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
 - To fix an issue with your account, file a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) in the Azure portal.
diff --git a/articles/mysql/single-server/single-server-whats-new.md b/articles/mysql/single-server/single-server-whats-new.md
@@ -132,11 +132,9 @@ This release of Azure Database for MySQL - Single Server includes the following
 - Added new stored procedures for control innodb buffer pool dump/restore.
 - Exposed the innodb warm up related server parameter for large storage server.
 
-## Contacts
+## Feedback and support
 
-If you have questions about or suggestions for working with Azure Database for MySQL, contact the Azure Database for MySQL Team ([@Ask Azure DB for MySQL](mailto:AskAzureDBforMySQL@service.microsoft.com)). This email address isn't a technical support alias.
-
-In addition, consider the following points of contact as appropriate:
+For any questions or suggestions you might have about working with Azure Database for MySQL flexible server, consider the following points of contact:
 
 - To contact Azure Support, [file a ticket from the Azure portal](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
 - To fix an issue with your account, file a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) in the Azure portal.
diff --git a/articles/mysql/single-server/whats-happening-to-mysql-single-server.md b/articles/mysql/single-server/whats-happening-to-mysql-single-server.md
@@ -220,11 +220,6 @@ When you migrate from Azure Database for MySQL - Single Server to Flexible Serve
 1. For *Problem type*, select **Migration**.
 1. For *Problem subtype*, select **Migrating from single to flexible server**
 
-You can also reach out to the Azure Database for MySQL product team at <AskAzureDBforMySQL@service.microsoft.com>.
-
-> [!WARNING]  
-> This article is not for Azure Database for MySQL - Flexible Server users. It is for Azure Database for MySQL - Single Server customers who need to upgrade to MySQL - Flexible Server.
-
 Visit the **[FAQ](../../dms/faq-mysql-single-to-flex.md)** for information about using the Azure Database Migration Service (classic) for Azure Database for MySQL - Single Server to Flexible Server migrations.
 
 We know migrating services can be a frustrating experience, and we apologize in advance for any inconvenience this might cause you. You can choose what scenario best works for you and your environment.
diff --git a/articles/postgresql/single-server/whats-happening-to-postgresql-single-server.md b/articles/postgresql/single-server/whats-happening-to-postgresql-single-server.md
@@ -224,8 +224,6 @@ The time taken for step #2 depends on the transactions that occur on the source.
 **A.** You can get further information in a few different ways.
 - Gett answers from community experts in [Microsoft Q&A](/answers/tags/214/azure-database-postgresql).
 
-- You can contact the [Azure Database for PostgreSQL product team](mailto:AskAzureDBforMySQL@service.microsoft.com?subject=Azure%20Database%20for%20PostgreSQL%20-%20Single%20Server%20retirement).
-
 - If you have a support plan and you need technical help, create a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest):
     - For Summary, type a description of your issue.
     - For Issue type, select Technical.
