Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Support Google-federated identities (Google Sign-In) in Microsoft Advertising connector OAuth flow

Answered
Lukka Maranhão User

Which connector?:

Microsoft Advertising

Additional details:

This feature request follows the resolution of support ticket #398782, which I opened with Fivetran. Support confirmed the limitation described below and directed me to submit it here as a feature request.

The Microsoft Advertising connector authorizes only through Microsoft's OAuth flow, which requires a Microsoft-native identity (Personal or Work/School account).

However, Microsoft Advertising itself allows users to sign in with Google Sign-In. Our users access Microsoft Advertising in the browser this way, but the connector authorization fails for them, as confirmed by Fivetran support in the ticket.

The current workaround is to re-provision the user as a Microsoft-native identity in the Microsoft Advertising admin portal. This requires admin action and creates credentials outside our identity provider (Google Workspace).

Feature request: allow the connector to be authorized by users whose Microsoft Advertising access was provisioned via Google Sign-In, so that re-provisioning a separate Microsoft-native account is not required.

This affects any organization on Google Workspace whose Microsoft Advertising users were created with Google Sign-In.

Reference: https://fivetran.com/docs/connectors/applications/microsoft-advertising/troubleshooting/unable-to-access-error

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Lucas Alexander Fivetranner

    Hi Lukka,

    Thanks for the detailed report and for following up here after your support ticket.

    You're correct that Microsoft added Google OAuth as an alternative authentication option for the Microsoft Advertising API in December 2025, alongside the existing Microsoft/Entra flow. The Fivetran Microsoft Advertising connector currently only supports the Microsoft/Entra flow, so accounts provisioned via Google Sign-In can't yet authorize the connector directly, which matches what you and support found.

    This is already tracked as an internal feature improvement to add Google OAuth as a second authentication option for the connector. I've linked your request to that existing work. While I can't share a specific timeline, I'll follow up on this thread when there's an update.

    Thanks for helping us improve the Microsoft Advertising connector!

    Cheers,
    Luke