August 2025 Recap: Azure Database for PostgreSQL
Hello Azure Community, August was an exciting month for Azure Database for PostgreSQL! We have introduced updates that make your experience smarter and more secure. From simplified Entra ID group login to integrations with LangChain and LangGraph, these updates help with improving access control and seamless integration for your AI agents and applications. Stay tuned as we dive deeper into each of these feature updates. Feature Highlights Enhanced Performance recommendations for Azure Advisor - Generally Available Entra-ID group login using user credentials - Public Preview New Region Buildout: Austria East LangChain and LangGraph connector Active-Active Replication Guide Enhanced Performance recommendations for Azure Advisor - Generally Available Azure Advisor now offers enhanced recommendations to further optimize PostgreSQL server performance, security, and resource management. These key updates are as follows: Index Scan Insights: Detection and recommendations for disabled index and index-only scans to improve query efficiency. Audit Logging Review: Identification of excessive logging via the pgaudit.log parameter, with guidance to reduce overhead. Statistics Monitoring: Alerts on server statistics resets and suggestions to restore accurate performance tracking. Storage Optimization: Analysis of storage usage with recommendations to enable the Storage Autogrow feature for seamless scaling. Connection Management: Evaluation of workloads for short-lived connections and frequent connectivity errors, with recommendations to implement PgBouncer for efficient connection pooling. These enhancements aim to provide deeper operational insights and support proactive performance tuning for PostgreSQL workloads. For more details read the Performance recommendations documentation. Entra-ID group login using user credentials - Public Preview The public preview for Entra-ID group login using user credentials is now available. This feature simplifies user management and improves security within the Azure Database for PostgreSQL. This allows administrators and users to benefit from a more streamlined process like: Changes in Entra-ID group memberships are synchronized on a periodic 30min basis. This scheduled syncing ensures that access controls are kept up to date, simplifying user management and maintaining current permissions. Users can log in with their own credentials, streamlining authentication, and improving auditing and access management for PostgreSQL environments. As organizations continue to adopt cloud-native identity solutions, this update represents a major improvement in operational efficiency and security for PostgreSQL database environments. For more details read the documentation on Entra-ID group login. New Region Buildout: Austria East New region rollout! Azure Database for PostgreSQL flexible server is now available in Austria East, giving customers in and around the region lower latency and data residency options. This continues our mission to bring Azure PostgreSQL closer to where you build and run your apps. For the full list of regions visit: Azure Database for PostgreSQL Regions. LangChain and LangGraph connector We are excited to announce that native LangChain & LangGraph support is now available for Azure Database for PostgreSQL! This integration brings native support for Azure Database for PostgreSQL into LangChain or LangGraph workflows, enabling developers to use Azure PostgreSQL as a secure and high-performance vector store and memory store for their AI agents and applications. Specifically, this package adds support for: Microsoft Entra ID (formerly Azure AD) authentication when connecting to your Azure Database for PostgreSQL instances, and, DiskANN indexing algorithm when indexing your (semantic) vectors. This package makes it easy to connect LangChain to your Azure-hosted PostgreSQL instances whether you're building intelligent agents, semantic search, or retrieval-augmented generation (RAG) systems. Read more at https://aka.ms/azpg-agent-frameworks Active-Active Replication Guide We have published a new blog article that guides you through setting up active-active replication in Azure Database for PostgreSQL using the pglogical extension. This walkthrough covers the fundamentals of active-active replication, key prerequisites for enabling bi-directional replication, and step-by-step demo scripts for the setup. It also compares native and pglogical approaches helping you choose the right strategy for high availability, and multi-region resilience in production environments. Read more about the active-active replication guide on this blog. Azure Postgres Learning Bytes 🎓 Enabling Zone-Redundant High Availability for Azure Database for PostgreSQL Flexible Server Using APIs. High availability (HA) is essential for ensuring business continuity and minimizing downtime in production workloads. With Zone-Redundant HA, Azure Database for PostgreSQL Flexible Server automatically provisions a standby replica in a different availability zone, providing stronger fault tolerance against zone-level failures. This section will guide you on how to enable Zone-Redundant HA using REST APIs. Using REST APIs gives you clear visibility into the exact requests and responses, making it easier to debug issues and validate configurations as you go. You can use any REST API client tool of your choice to perform these operations including Postman, Thunder Client (VS Code extension), curl, etc. to send requests and inspect the results directly. Before enabling Zone-Redundant HA, make sure your server is on the General Purpose or Memory Optimized tier and deployed in a region that supports it. If your server is currently using Same-Zone HA, you must first disable it before switching to Zone-Redundant. Steps to Enable Zone-Redundant HA: Get an ARM Bearer token: Run this in a terminal where Azure CLI is signed in (or use Azure Cloud Shell) az account get-access-token --resource https://management.azure.com --query accessToken -o tsv Paste token in your API client tool Authorization: `Bearer <token>` </token> Inspect the server (GET) using the following URL: https://management.azure.com/subscriptions/{{subscriptionId}}/resourceGroups/{{resourceGroup}}/providers/Microsoft.DBforPostgreSQL/flexibleServers/{{serverName}}?api-version={{apiVersion}} In the JSON response, note: sku.tier → must be 'GeneralPurpose' or 'MemoryOptimized' properties.availabilityZone → '1' or '2' or '3' (depends which availability zone that was specified while creating the primary server, it will be selected by system if the availability zone is not specified) properties.highAvailability.mode → 'Disabled', 'SameZone', or 'ZoneRedundant' properties.highAvailability.state → e.g. 'NotEnabled','CreatingStandby', 'Healthy' If HA is currently SameZone, disable it first (PATCH) using API. Use the same URL in Step 3, in the Body header insert: { "properties": { "highAvailability": { "mode": "Disabled" } } } Enable Zone Redundant HA (PATCH) using API: Use the same URL in Step 3, in the Body header insert: { "properties": { "highAvailability": { "mode": "ZoneRedundant" } } } Monitor until HA is Healthy: Re-run the GET from Step 3 every 30-60 seconds until you see: "highAvailability": { "mode": "ZoneRedundant", "state": "Healthy" } Conclusion That’s all for our August 2025 feature updates! We’re committed to making Azure Database for PostgreSQL better with every release, and your feedback plays a key role in shaping what’s next. 💬 Have ideas, questions, or suggestions? Share them with us: https://aka.ms/pgfeedback 📢 Want to stay informed about the latest features and best practices? Follow us here for the latest announcements, feature releases, and best practices: Azure Database for PostgreSQL Blog More exciting improvements are on the way—stay tuned for what’s coming next!MGDC for SharePoint FAQ: Which regions are supported? Updated in September 2025
1. Overview When gathering SharePoint data through Microsoft Graph Data Connect (MGDC), you need to pay attention to an important detail: regions. That includes both the region of your Microsoft 365 tenant (the data source), the region of the Azure Storage account (the data destination) and the region of your workspace where you run your pipelines. In this blog, we’ll investigate the importance of understanding regions, which regions are supported by SharePoint on MGDC, the requirement to use a matching region in Azure, and how to handle a tenant with data in multiple regions. We will also share the additional regions supported as of September 2025. 2. Regions When you use MGDC to pull data from your SharePoint tenant to an Azure account, you always do this in the context of a region. The region is the geographic location where Microsoft stores your data. MGDC and SharePoint support extracting data from several Microsoft 365 regions. As I write this blog, those regions include all three macro regions (Asia-Pacific, Europe and North America), plus many of the go-local regions (like Australia, Brazil and Canada). 3.Which regions are supported by SharePoint on MGDC? To move data from Microsoft 365 tenant to your Azure account, both must map to a supported region for MGDC. On the Microsoft 365 side, the data location for the SharePoint data must be supported. On the Azure side, the region for your storage account, your Synapse workspace and your Azure Data Factory instance must be supported. Here is the list of Microsoft 365 and Azure regions supported: Microsoft 365 region Azure region SharePoint Datasets* All Other Datasets Asia-Pacific (APC) East Asia Southeast Asia Y Y Australia (AUS) Australia East Australia Southeast Y Y Brazil (BRA) Brazil South Y Y Canada (CAN) Canada Central Canada East Y Y Europe (EUR) North Europe West Europe Y Y France (FRA) France Central Y Y Germany (DEU) Germany West Central Y Y India (IND) South India Central India Y Y Israel (ISR) Israel Central Y N Italy (ITA) Italy North Y N Japan (JPN) Japan West Japan East Y Y Korea (KOR) Korea Central Korea South Y Y Mexico (MEX) Mexico Central Y N North America (NAM) Central US East US East US 2 North Central US South Central US West Central US West US West US 2 Y Y Norway (NOR) Norway East Y Y Poland (POL) Poland Central Y N Qatar (QAT) Qatar Central Y N South Africa (ZAF) South Africa North Y N Spain (ESP) Spain Central Y N Sweden (SWE) Sweden Central Y N Switzerland (CHE) Switzerland North Y Y UAE (UAE) UAE North Y Y United Kingdom (GBR) UK South UK West Y Y Note: Some of the regions (the ones that were added most recently) are supported only for the SharePoint datasets in Microsoft Graph Data Connect. That includes Sites, Groups, Permissions, File and File Actions. These recently added regions are not supported for OneDrive, Exchange, Teams and other Microsoft Graph Data Connect datasets. 4. The regions must match So, you need both your Microsoft 365 (Office) region and your Azure region to be supported (listed in the table above). Beyond that, you must also make sure that the Microsoft 365 regions and the Azure regions match. For instance, if your Office region is Europe, you must use an Azure storage account in either North Europe or West Europe. If you try to pull data for a tenant in the Australia Office region from an Azure account in West US, it will not work. You will basically get no data in this scenario. Even though these are both supported regions, they do not match. Please note that Microsoft 365 offers local regions in certain geographies, like Germany, France and Norway. Although these are countries in Europe, these country-specific Microsoft 365 regions (also known as go-locals) are not included in the Microsoft 365 Europe region. 5. How do I find my Microsoft 365 (Office) region? You can use the Microsoft 365 Admin Center to find the region for your tenant. The URL for the Admin center is https://admin.microsoft.com. You will find this information under “Show all”, “Settings”, “Org settings”. Then select the tab for “Organizational Settings” and select “Data location”. Here are some sample screenshots: If your tenant is not in one of the supported SharePoint on MGDC regions, please reach out to help us prioritize which regions we should add in the future. 6. How do I find my Azure account region? When you create Azure resources like a Storage account, you must specify the region where you want your data to be stored. This also applies to other resources in Azure like your Azure Synapse workspace or your Azure Data Factory instance. See below a list of storage accounts in Azure, showing the region (location): 7. What if my tenant uses multiple regions? It is possible for a Microsoft 365 tenant to have data in multiple regions. This single tenant can choose to have some OneDrive and SharePoint sites in one region and another set of OneDrive and SharePoint sites in a different region. This multi-geo capability is commonly used by large, multi-national companies. For these tenants, MGDC for SharePoint will only allow you to pull data for one region at a time, using an Azure account that matches that region. For instance, if your tenant has sites in North America and Europe, you will need to pull data from an Azure account in North America to get the north American sites and another Azure account in Europe to pull the European sites. The priority is to keep the data from the different regions separate, for compliance reasons. Once the multiple datasets are transferred to the multiple Azure accounts, you could join them into a single account, if your tenant’s compliance requirements allow for that. 8. What kind of error will I see? If you use an unsupported region, you will see an error like this: Operation on target <ActivityName> failed: ErrorCode=UserErrorOffice365DataLoaderError, ‘Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException, Message=Office365 data loading failed to execute. office365LoadErrorType: PermanentError. Dataset: <DatasetName> is not available in the region: <UnsupportedRegion>, Source=Microsoft.DataTransfer.ClientLibrary,’ 9. Summary This blog announced additional Microsoft 365 and Azure regions supported in MGDC for SharePoint. For more information about SharePoint Data in MGDC, please visit the collection of links at https://aka.ms/SharePointData.
