Community

Other: Microsoft Bing Advertising destination support in Census Terraform provider

Answered

Airam Fuentes Contreras User

February 20, 2026 10:53

Summary

Add support for Microsoft Bing Advertising as a destination type in the Census Terraform provider so customers can create and manage Bing Ads destinations and their syncs via Infrastructure as Code.

Current situation

We use the Census Terraform provider (sutrolabs/census v0.2.10) to manage our Fivetran activations. We can create and manage destinations such as Google Ads and Meta (Facebook) and assign syncs from our Snowflake source via Terraform. Microsoft Bing Advertising is not currently supported as a destination in the provider, and support confirmed it is not on the roadmap.

What we’re trying to do

Create a Microsoft Bing Advertising destination connection using Terraform.

Assign data syncs from our Snowflake source to this Bing destination.

Manage these resources as IaC so all our advertising destinations (Google, Meta, Bing, etc.) are configured and versioned in the same way.

Why this matters

Consistency: We’d manage all major ad destinations (Google, Meta, Bing) through the same Terraform workflow.

Automation & safety: New environments and changes would go through plan/apply and version control instead of manual UI setup.

Scalability: As we add more Bing syncs or accounts, we avoid manual, error-prone configuration.

We’d like to request that Microsoft Bing Advertising be added as a supported destination type in the Census Terraform provider so we can include it in our IaC setup. We’re happy to provide more detail or use cases if that would help with prioritization.

Thank you for considering this.

Please sign in to leave a comment.

Comments

3 comments

Official comment

Amanda Wong User
- March 05, 2026 17:18
Hi Airam,
This is a valuable idea and we have added your request for Microsoft Bing Advertising support in the Census Terraform provider to our feature improvements backlog.
We will keep the community updated on this thread with any progress.
Thanks,
Amanda

Hadley Killen User

March 05, 2026 18:21

Hi Airam!

We have released support for creating Microsoft Ads destinations via API (and thus via terraform). Example terraform -

# Creates a Microsoft Advertising destination using customer-provided OAuth credentials.
resource "census_destination" "microsoft_advertising" {
  workspace_id = var.workspace_id
  name         = "Microsoft Advertising (Terraform)"
  type         = "microsoft_advertising"
  connection_config = {
    access_token            = var.microsoft_access_token
    refresh_token           = var.microsoft_refresh_token
    access_token_expires_in = var.microsoft_access_token_expires_in
    client_id               = var.microsoft_client_id
    client_secret           = var.microsoft_client_secret
    developer_token         = var.microsoft_developer_token
    account_id              = var.microsoft_account_id
    account_name            = var.microsoft_account_name
    customer_id             = var.microsoft_customer_id
    customer_name           = var.microsoft_customer_name
  }
}

more details on these parameters -

Field	Required	Description
`access_token`	Yes	OAuth 2.0 access token from your Microsoft OAuth app. Obtained by completing the OAuth authorization flow with Microsoft's `<https://login.microsoftonline.com/common/oauth2/v2.0/authorize`> endpoint.
`refresh_token`	Recommended	OAuth 2.0 refresh token. If provided, Census will automatically refresh expired access tokens on your behalf. Without this, the connection will stop working when the access token expires.
`access_token_expires_in`	Recommended	Lifetime of the access token in seconds (e.g. `3600`). Required if `refresh_token` is provided.
`client_id`	Recommended	The Application (client) ID of your registered Microsoft OAuth app. Required if `refresh_token` is provided, so Census can refresh tokens using your app.
`client_secret`	Recommended	The client secret from your registered Microsoft OAuth app. Required if `refresh_token` is provided.
`developer_token`	Optional	Your Microsoft Advertising API developer token. Obtained from the Microsoft Advertising Developer Portal. If not provided, Census will use its own developer token.
`account_id`	Optional	The Microsoft Advertising account ID to sync data to. Can be set later via `PATCH /api/v1/destinations/:id`, but must be set before syncing to this destination.
`account_name`	Optional	The user facing Name of the Microsoft Advertising account to sync data to.
`customer_id`	Optional	The Microsoft Advertising customer ID that owns the account. Required if `account_id` is provided. Each account belongs to a customer; both are needed for API calls.
`customer_name`	Optional	The user facing Name of the Microsoft Advertising customer that owns the account.

This matches how we support creating other OAuth destinations via API (Google Ads & Facebook Ads). Please try this out and let me know if this works for your use case!

Thanks,

Hadley

Airam Fuentes Contreras User
- March 09, 2026 14:30
Thank you very much for considering it