Why should you care?

Enterprises on Azure stack host DataFlow beside App Service and Key Vault without cross-cloud egress.

See it live — copy this example

Run in MySQL Workbench or the mysql CLI.

CREATE USER 'dataflow_app'@'%' IDENTIFIED BY 'VaultStoredPassword!';
GRANT SELECT, INSERT, UPDATE, DELETE ON DataFlow.* TO 'dataflow_app'@'%';
-- JDBC/Node host:
-- dataflow-prod.mysql.database.azure.com
-- user: dataflow_app@dataflow-prod (server name suffix rule)

What happened?

• Flexible Server uses familiar GRANT SQL.
• Azure often requires username@servername format in older drivers.
• Store password in Key Vault; enable SSL enforcement in server settings.

Practice next

1. Create Flexible Server in Azure portal.
2. Configure firewall to allow Azure services or your IP.
3. Connect from Workbench with SSL required.
4. Enable geo-redundant backup for DR story.
5. Compare burstable vs general purpose SKU pricing.

Remember

Azure managed MySQL with VNet and backups. Same SQL GRANT patterns as on-prem. Integrate secrets with Key Vault.

DataFlow on Azure

.NET + Node services in App Service hit Flexible Server in same region.

Outcome: Single cloud bill and private VNet path.