Releasesby GlyphLakehouse : Cross-cloud Lakehouse now supports integration with SAP Business Data Cloud (BDC) in Preview
Lakehouse : Cross-cloud Lakehouse now supports integration with SAP Business Data Cloud (BDC) in Preview. This update includes the following features: Federation from SAP BDC: Create Delta Sharing catalogs in Lakehouse to automatically synchronize shares, schemas, and tables from SAP BDC.
Also shipped Jul 20, 2026Google Cloud in July 2026 →
OIDC federated authentication (Public Preview)
OpenID Connect (OIDC) security integrations for federated single sign-on (SSO) are available in Public Preview. Multiple OIDC integrations, or OIDC alongside an existing SAML2 integration, require identifier-first login . Without identifier-first login, only one SSO integration (SAML2 or OIDC) can be ENABLED=TRUE at a time.
DML into frozen regions of dynamic tables (General availability)
You can now use DML statements (INSERT, UPDATE, MERGE, DELETE) to modify rows directly in the frozen region of a dynamic table. This enables use cases such as GDPR-required row deletions or correcting specific records without triggering a full refresh of the active region. For more information, see DML into a frozen region .
Pass-through policies for dynamic tables with incremental refresh (General availability)
Dynamic tables that have base tables with arbitrary masking or row access policies can now maintain incremental refresh when the policy is pass-through for the role used during refresh (that is, when the refresh role has unrestricted access to all rows and columns regardless of the policy condition).
[In preview] Public Preview: Protect sensitive generative AI telemetry in Application Insights and Microsoft Foundry
Azure Monitor Application Insights now stores generative AI content in a dedicated GenAIContent table (AppGenAIContent in Log Analytics), making it possible to apply newly available access controls to sensitive AI telemetry. Because Application Insights p
AI credit pools for cost centers in the billing UI
You can now manage a cost center’s AI credit pool directly in the billing UI where you create and edit cost centers. Previously, you could only manage this through the GitHub REST API. This feature is available for Copilot Business and Copilot Enterprise on GitHub Enterprise Cloud. Toggle the AI credit pool on when you create or edit a cost center.
Copilot users can now see AI credits used per billing cycle
Copilot Business and Copilot Enterprise users can now see how many AI credits they’ve used this billing cycle, even without an individual budget. Find this on your GitHub Copilot usage page in your GitHub settings. Previously, the page showed usage only as a percentage of a budget.
More from BigQueryEvery BigQuery release →
BigQuery supports data governance tags , which let you enforce column-level security and data masking
BigQuery supports data governance tags , which let you enforce column-level security and data masking. Data governance tags are a type of Resource Manager tag that you can attach to sensitive columns and use in BigQuery data policies to grant conditional access to your users. This feature is in Preview .
Conversational analytics now supports the AI.AGG function
Conversational analytics now supports the AI.AGG function . This function is in Preview .
You can discover commercial BigQuery sharing listings on Google Cloud Marketplace with the Marketplace filter
You can discover commercial BigQuery sharing listings on Google Cloud Marketplace with the Marketplace filter. For more information, see Subscribe to a Cloud Marketplace-integrated listing . This feature is generally available (GA).
BigQuery APPENDS and CHANGES change history functions are GA
The APPENDS and CHANGES functions return the rows appended to or changed in a table over a time range, useful for incremental processing and auditing.
Google-developed ODBC driver for BigQuery is generally available
Applications can connect to BigQuery using the Google-developed Open Database Connectivity (ODBC) driver, now generally available.
BigQuery renames insertAll to Storage Write API (REST)
The legacy tabledata.insertAll method is now called the Storage Write API (REST), and the existing Storage Write API is now the Storage Write API (gRPC).