Announcing the Public Preview of Reader Endpoint for Azure Database for MySQL
We are excited to announce the Public Preview of Reader Endpoint for Azure Database for MySQL. Read replicas help applications scale read-intensive workloads by moving read traffic away from the primary server. This can include traditional applications, analytics and reporting workloads, and AI-powered applications that retrieve structured context from MySQL. However, as the number of replicas grows, applications traditionally need to maintain separate replica hostnames and implement their own connection-routing logic. Reader Endpoint simplifies that experience. It provides a single DNS endpoint for read replicas and automatically distributes new read connections across eligible replicas. Applications can use one connection endpoint instead of managing every replica individually. Simplified read scaling through one endpoint Reader Endpoint uses connection-level routing and continuously monitors replica availability and replication lag. If a replica becomes unavailable or exceeds the configured replication-lag threshold, Reader Endpoint automatically excludes it from routing. Reader Endpoint does not inspect individual queries and does not route write traffic. Applications should continue directing writes to the primary server. Choose the routing method that fits your workload Reader Endpoint supports two routing methods: Rotational routing: Distributes connections across eligible replicas in a round-robin pattern. Performance routing: Uses geographic proximity to route connections to eligible replicas in the region closest to the client. This gives application teams the flexibility to distribute connections evenly or prioritize geographic proximity. Configure routing for your application’s needs Reader Endpoint allows you to configure: The read replicas that participate in routing The maximum acceptable replication lag for an eligible replica DNS time to live, including a TTL value of 0 Whether the primary server can serve reads when no eligible replica is available Whether newly created replicas are automatically attached to the endpoint Configure the Reader Endpoint name, routing method, DNS TTL, and replication-lag threshold. Select participating replicas and configure fallback and automatic replica attachment. You can also create multiple Reader Endpoints for the same source server. This enables different applications or workloads to use their own replica selections, routing methods, lag thresholds, and DNS TTL settings. For example, an operational application could use one endpoint with a strict replication-lag threshold, while a reporting workload could use another endpoint with a different set of replicas and routing configuration. What is new in Public Preview? Building on the Private Preview, the Public Preview introduces several enhancements: Support for multiple Reader Endpoints per source server The new Performance routing method, alongside Rotational routing Support for configuring DNS TTL to 0 An option to allow the primary server to serve reads when no eligible replica is available Automatic attachment of newly created replicas Scale data retrieval for AI-powered applications AI-powered applications can generate significant read traffic when retrieving structured context, such as product, customer, or application data, from MySQL. Reader Endpoint helps scale these read-intensive operations by distributing new connections across eligible read replicas through a single endpoint. Applications can also use a separate Reader Endpoint for AI workloads, with their own replica selection, routing method, and replication-lag threshold. Other common scenarios Reader Endpoint can simplify connection management for several read-intensive scenarios: Applications that need to scale read traffic across multiple replicas Business intelligence, analytics, and reporting workloads Read-only microservices Applications that need to avoid routing new connections to unavailable or lagging replicas Different workloads requiring independent replica and routing configurations Public Preview considerations The following limitations currently apply: Support for changing the routing method after endpoint creation will be added in an upcoming update. Azure CLI is not yet supported for Reader Endpoint. You can't use SSL connections that use VERIFY_IDENTITY mode through the reader endpoint. Other SSL modes are supported. Reader Endpoint incurs an additional charge. Use the Azure Pricing Calculator to estimate applicable costs. Get started To learn more about routing behaviour, configuration options, pricing, and current limitations, see Read replicas in Azure Database for MySQL. We encourage you to try Reader Endpoint with your read-intensive workloads and share your feedback as we continue improving the experience toward general availability. We invite you to share your experiences or suggestions at AskAzureDBforMySQL@service.microsoft.com Thank you for choosing Azure Database for MySQL!Ignite 2025: Advancing Azure Database for MySQL with Powerful New Capabilities
At Ignite 2025, we’re introducing a wave of powerful new capabilities for Azure Database for MySQL, designed to help organizations modernize, scale, and innovate faster than ever before. From enhanced high availability and seamless serverless integrations to AI-powered insights and greater flexibility for developers, these advancements reflect our commitment to delivering a resilient, intelligent data platform. Join us as we unveil what’s next for MySQL on Azure - and discover how industry leaders are already building the future with confidence. Enhanced Failover Performance with Dedicated SLB for High-Availability Servers We’re excited to announce the General Availability of Dedicated Standard Load Balancer (SLB) for HA-enabled servers in Azure Database for MySQL. This enhancement introduces a dedicated SLB to High Availability configurations for servers created with public access or private link. By managing the MySQL data traffic path, SLB eliminates the need for DNS updates during failover, significantly reducing failover time. Previously, failover relied on DNS changes, which caused delays due to DNS TTL (30 seconds) and client-side DNS caching. What’s new with GA: The FQDN consistently resolves to the SLB IP address before and after failover. Load-balancing rules automatically route traffic to the active node. Removes DNS cache dependency, delivering faster failovers. Note: This feature is not supported for servers using private access with VNet integration. Learn more Build serverless, event-driven apps at scale – now GA with Trigger Bindings for Azure Functions We’re excited to announce the General Availability of Azure Database for MySQL Trigger bindings for Azure Functions, completing the full suite of Input, Output, and Trigger capabilities. This feature lets you build real-time, event-driven applications by automatically invoking Azure Functions when MySQL table rows are created or updated - eliminating custom polling and boilerplate code. With native support across multiple languages, developers can now deliver responsive, serverless solutions that scale effortlessly and accelerate innovation. Learn more Enable AI agents to query Azure Database for MySQL using Azure MCP Server We’re excited to announce that Azure MCP Server now supports Azure Database for MySQL, enabling AI agents to query and manage MySQL data using natural language through the open Model Context Protocol (MCP). Instead of writing SQL, you can simply ask questions like “Show the number of new users signed up in the last week in appdb.users grouped by day.”, all secured with Microsoft Entra authentication for enterprise-grade security. This integration delivers a unified, secure interface for building intelligent, context-aware workflows across Azure services - accelerating insights and automation. Learn more Greater networking flexibility with Custom Port Support Custom port support for Azure Database for MySQL is now generally available, giving organizations the flexibility to configure a custom port (between 25001 and 26000) during new server creation. This enhancement streamlines integration with legacy applications, supports strict network security policies, and helps avoid port conflicts in complex environments. Supported across all network configurations - including public access, private access, and Private Link - custom port provisioning ensures every new MySQL server can be tailored to your needs. The managed experience remains seamless, with all administrative capabilities and integrations working as before. Learn more Streamline migrations and compatibility with Lower Case Table Names support Azure Database for MySQL now supports configuring lower_case_table_names server parameter during initial server creation for MySQL 8.0 and above, ensuring seamless alignment with your organization’s naming conventions. This setting is automatically inherited for restores and replicas, and cannot be modified. Key Benefits: Simplifies migrations by aligning naming conventions and reducing complexity. Enhances compatibility with legacy systems that depend on case-insensitive table names. Minimizes support dependency, enabling faster and smoother onboarding. Learn more Unlock New Capabilities with Private Preview Features at Ignite 2025 We’re excited to announce that you can now explore two powerful capabilities in early access - Reader Endpoint for seamless read scaling and Server Rename for greater flexibility in server management. Scale reads effortlessly with Reader Endpoint (Private Preview) We’re excited to announce that the Reader Endpoint feature for Azure Database for MySQL is now ready for private preview. Reader Endpoint provides a dedicated read-only endpoint for read replicas, enabling automatic connection-based load balancing of read-only traffic across multiple replicas. This simplifies application architecture by offering a single endpoint for read operations, improving scalability and fault tolerance. Azure Database for MySQL supports up to 10 read replicas per primary server. By routing read-only traffic through the reader endpoint, application teams can efficiently manage connections and optimize performance without handling individual replica endpoints. Reader endpoints continuously monitor the health of replicas and automatically exclude any replica that exceeds the configured replication lag threshold or becomes unavailable. To enroll in the preview, please submit your details using this form. Limitations During Private Preview: Only performance-based routing is supported in this preview. Certain settings such as routing method and the option to attach new replicas to the reader endpoint can only be configured at creation time. Only one reader endpoint can be created per replica group. Including the primary server as a fallback for read traffic when no replicas are available is not supported in this preview. Get flexibility in server management with Server Rename (Private Preview) We’re excited to announce the Private Preview of Server Rename for Azure Database for MySQL. This feature lets you update the name of an existing MySQL server without recreating it, migrating data, or disrupting applications - making it easier to adopt clear, consistent naming. It provides a near zero-downtime path to a new hostname of the server. To enroll in the preview, please submit your details using this form. Limitations During Private Preview: Primary server with read replicas: Renaming a primary server that has read replicas keeps replication healthy. However, the SHOW SLAVE STATUS output on the replicas will still display the old primary server's name. This is a display inconsistency only and does not affect replication. Renaming is currently unsupported for servers using Customer Managed Key (CMK) encryption or Microsoft Entra Authentication (Entra Id). Real-World Success: Azure Database for MySQL Powers Resilient Applications at Scale Factorial Factorial, a leading HR software provider, uses Azure Database for MySQL alongside Azure Kubernetes Service to deliver secure, scalable HR solutions for thousands of businesses worldwide. By leveraging Azure Database for MySQL’s reliability and seamless integration with cloud-native technologies, Factorial ensures high availability and rapid innovation for its customers. Learn more YES (Youth Employment Service) South Africa’s largest youth employment initiative, YES, operates at national scale by leveraging Azure Database for MySQL to deliver a resilient, centralized platform for real-time job matching, learning management, and career services - connecting thousands of young people and employers, and helping nearly 45 percent of participants secure permanent roles within six months. Learn more Nasdaq At Ignite 2025, Nasdaq will showcase how it uses Azure Database for MySQL - alongside Azure Database for PostgreSQL and other Azure products - to power a secure, resilient architecture that safeguards confidential data while unlocking new agentic AI capabilities. Learn more These examples demonstrate that Azure Database for MySQL is trusted by industry leaders to build resilient, scalable applications - empowering organizations to innovate and grow with confidence. We Value Your Feedback Azure Database for MySQL is built for scale, resilience, and performance - ready to support your most demanding workloads. With every update, we’re focused on simplifying development, migration, and management so you can build with confidence. Explore the latest features and enhancements to see how Azure Database for MySQL meets your data needs today and in the future. We welcome your feedback and invite you to share your experiences or suggestions at AskAzureDBforMySQL@service.microsoft.com Stay up to date by visiting What's new in Azure Database for MySQL, and follow us on YouTube | LinkedIn | X for ongoing updates. Thank you for choosing Azure Database for MySQL!
