An Azure managed MySQL database service for app development and deployment.
Hi @Cedric Ahlers
It looks like you're trying to configure user-defined routes for your Azure MySQL and PostgreSQL Flexible Servers in a private access deployment. Understandably, getting this routing right can be tricky, especially with your Hub and Spoke network setup.
Routing Requirements: When using private access for Azure Database services, here are a few points to consider based on the documentation:
User-Defined Routes: Azure Database for MySQL and PostgreSQL Flexible Servers support user-defined routes, but specific configuration depends on your setup. You mentioned needing reliable documentation; while it's true that the official docs don't extensively cover every detail, a few essential routes are often necessary:
- Ensure the
VNetLocalandAzureActiveDirectoryservice tags are present in your route tables.- Routes must also allow traffic to and from your Flexible Servers and any related resources.
- For your setup, you should typically allow routes for the service tags related to Azure Database services. Relevant service tags generally include: - `Sql` (for Azure SQL services) - `AzureDatabase` (which may encompass MySQL and PostgreSQL) - Additionally, the tags you specifically choose to route directly to the Internet will depend on your use case (e.g., if you're using Azure Blob Storage or other endpoints). **Adjust Routing**: Following your star topology, you’d route `0.0.0.0/0` through the Azure Firewall and selectively route the necessary service tags to the Internet, as per your requirement. **Documentation**: For further reference, I’ve included some links below to help you along the way: