Azure Database for MySQL and Azure Database for PostgreSQL Resource GUID migration

Thank you for being a customer of Azure database services for MySQL and PostgreSQL during preview. Based customer feedback during preview, we are making some changes to our business and pricing model that simplify purchasing and offer more flexibility.

Starting February 28, 2018, customers can expect the following changes that will affect their currently provisioned Azure Database for MySQL or PostgreSQL services:

• Compute charges will be changed from Compute unit to vCore, providing more transparency about the hardware configuration for MySQL or PostgreSQL server.
• For more flexibility, storage will no longer will be included with compute. Customers can provision the storage they need, and scale compute and storage independently. As part of the new business model, you’ll see your storage already provisioned at the level you had before.
• There will be no charge for back up storage, up to 1X provisioned storage of your database server.
• Network egress will be charged as per standard Azure rates. For more information, please visit the Bandwidth Pricing Details webpage.
• Preview pricing will remain in effect under the new business model.
• A change to the Resource GUIDs used to track usage will appear on your invoices. Your applications or databases will not require any code changes.

To see the impact on existing resource GUIDs in all regions, please reference the table below. Your applications or databases will not require any code changes.