In short: Since December 2025 the Bing Ads API accepts Google sign-in — the new GoogleOAuthDesktopMobileAuthCodeGrant and GoogleOAuthWebAuthCodeGrant grants let you authenticate Microsoft Advertising with the same Google identity you already use for Google Ads. A March 2026 fix preserved the refresh token. It's onboarding friction removed, not a new capability — one auth model across both platforms, less code to maintain.
A small change with outsized convenience: since December 2025 the Bing Ads API accepts Google sign-in. The new grants — GoogleOAuthDesktopMobileAuthCodeGrant and GoogleOAuthWebAuthCodeGrant — let you authenticate the Microsoft Advertising API with the same Google identity you already use for Google Ads. A March 2026 fix closed an early gap by preserving the Google refresh token.
Why it matters
Cross-platform tooling has always paid an auth tax: two identity providers, two token lifecycles, two sets of credential-management code. Folding Microsoft into Google OAuth means one mental model across both platforms — and meaningfully less code to manage in any tool that touches both. ALM Corp’s walkthrough covers the onboarding flow in detail.
This is onboarding friction removed, not a new capability — but for agencies and multi-account scripts, less auth plumbing is exactly the kind of change that quietly makes everything else easier to build.
How to use it
If you’re building or refactoring a multi-platform connector, unify the auth layer under one Google OAuth flow rather than maintaining a separate Microsoft credential path. Pick the grant that matches your runtime: GoogleOAuthWebAuthCodeGrant for a server-side app with a redirect URI, GoogleOAuthDesktopMobileAuthCodeGrant for installed tooling. Store and refresh the Google token exactly as you already do for Google Ads — the March 2026 fix means the refresh token now survives, so you’re not re-prompting users on every session.
It pairs naturally with the year’s other convergence wins — richer Google import, AI Max parity, New Customer Acquisition import from Google PMax. One identity, two platforms, less code between them.
The catch worth flagging: a shared identity is also a shared point of failure, so treat the Google token’s storage and rotation with the same care you’d give a Microsoft credential. Convenience at the auth layer is only a win if the security posture comes with it.
For the full sweep of where the Microsoft Advertising API caught up to Google this year, see our Microsoft API year in review.
