https://clientcenter.api.bingads.microsoft.com/CustomerManagement/v13). It uses a developer token plus a Microsoft sign-in (OAuth refresh token) for one Microsoft Advertising user. Configview only reads. It never creates, changes or deletes anything in Microsoft Advertising.
You will end up with 3 required secrets (MSADS_DEVELOPER_TOKEN, MSADS_CLIENT_ID, MSADS_REFRESH_TOKEN) and 2 optional ones (MSADS_CLIENT_SECRET, MSADS_CUSTOMER_ID) in Configview when setup is complete.
Scope of this integration today. Configview reads the customer, its ad accounts (status, pause reason, currency, time zone, billing threshold), every user with their role and Super Admin status, role by ad account, pending user invitations, and the agencies or other customers linked to your accounts. It does not read campaigns, ads, keywords, audiences, conversion data, payment methods or reporting data. The API has no audit log, no last-sign-in time and no 2-step verification flag, so none of those are collected. Account spend per day needs the asynchronous Reporting service and is not collected yet.
Read this first: the sign-in is a refresh token
Microsoft Advertising has no API key and no app-only (service principal) login. Every call needs the sign-in of a real Microsoft Advertising user. Configview stores that user’s refresh token and redeems it for a short-lived access token on every run.- Microsoft documents that refresh tokens “do not have specified lifetimes” and that they can be invalidated at any moment (password change, consent withdrawn, sign-in policy). Plan on replacing the token about every 90 days and whenever the Verify now check says Microsoft refused it.
- Configview cannot save the new refresh token that Microsoft may return when one is redeemed. Microsoft states that the old refresh token is not revoked when it is used, so the stored one keeps working until it expires or is revoked. When it stops working, repeat Step 3 and replace
MSADS_REFRESH_TOKEN. - Use a dedicated user (for example
configview@yourcompany.com), not a person, so the token does not stop when someone leaves. Microsoft Advertising requires multi-factor authentication for sign-in, so set that up on the user. - The token carries everything the user can do. Give the user the Viewer role and the Microsoft Advertising scope only.
What you need
- A Microsoft Advertising customer with at least one account
- A Super Admin to request the developer token and to invite the dedicated user
- A Microsoft Entra tenant where you can register an application (this is only to get a client ID; no admin consent is needed)
Step 1: Open the Microsoft Advertising page in Configview
Open Configview in a second browser tab and leave it open:https://{companyname}.configview.com/admin/integrations/microsoft-ads
Step 2: Developer token
- Sign in at
https://developers.ads.microsoft.com/Accountas a Super Admin. - Click Request Token. A universal developer token works for every account.
- Paste it into
MSADS_DEVELOPER_TOKENin Configview and click the save icon.
Step 3: Application and refresh token
-
In the Microsoft Entra admin center open App registrations, New registration. Name it
Configview. For Supported account types choose Any Entra ID Tenant + Personal Microsoft accounts. Add the redirect URIhttps://login.microsoftonline.com/common/oauth2/nativeclient(platform: public client). -
Copy the Application (client) ID into
MSADS_CLIENT_ID. If you created a client secret (web app), paste it intoMSADS_CLIENT_SECRET; leave it empty for a public client. - Invite the dedicated user in Microsoft Advertising (Tools, Users, Add user) with the Viewer role, accept the invitation, and sign in once.
-
In a private browser window, signed in as that user, open this address (one line, replace
CLIENT_ID):https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=CLIENT_ID&response_type=code&redirect_uri=https://login.microsoftonline.com/common/oauth2/nativeclient&scope=openid%20profile%20https://ads.microsoft.com/msads.manage%20offline_access&prompt=consent -
Approve. The browser lands on a blank page whose address contains
code=.... Copy the value ofcode(up to the next&). -
Exchange it for a refresh token from a terminal (add
-d client_secret=...if you use one): -
Copy
refresh_tokenfrom the answer intoMSADS_REFRESH_TOKENin Configview. The code can be used only once and expires in minutes.
AADSTS650052, your tenant has no Microsoft Advertising service principal yet; a Microsoft Advertising user signing in once, or an Entra admin consenting to application d42ffc93-c136-491d-b4fd-6f18168c68fd, creates it.
Step 4 (optional): Customer ID
By default Configview reads every customer on the signed-in user’s role list. To limit it, put one or more comma-separated customer ids inMSADS_CUSTOMER_ID.
Step 5: Connect and verify
- Click Connect. Configview creates its tables and schedules every collector at your default run time:
- Click Verify now. The health check reads the three required secrets, redeems the refresh token and calls GetUser.
- Refresh token refused (
invalid_grant). The token expired or was revoked. Repeat Step 3. - 401 from GetUser. The developer token is wrong or was never approved, or the user has no Microsoft Advertising access.
- Agency and client links skipped. The user is a Viewer. Only Super Admin or Standard users can search links. Accept the gap or use a higher role.
Data Tables
Each table has arun_at column and keeps only the newest run.
Things worth knowing
Roles. 41 Super Admin (everything, including users and billing), 203 Standard User, 16 Advertiser Campaign Manager, 100 Viewer (read only), 33 Aggregator (agency role). A role with no account list covers the whole customer;msads_user_roles.account_id is empty for it.
Agencies. A client link means another Microsoft Advertising customer (an agency) manages one of your accounts or your whole customer. Review the active ones.
Pending invitations expire after 30 days and are removed from the list when accepted.
Rate limit. Customer Management documents no request limit. Configview paces itself at 60 requests a minute and waits as long as Microsoft asks after an HTTP 429.
What isn’t collected
- Campaigns, ad groups, ads, keywords, audiences, creatives and landing pages
- Conversion, pixel and reporting data, and account spend (the Reporting service is asynchronous and not used yet)
- Payment methods, business addresses, user phone numbers and postal addresses
- OAuth tokens and secrets (they stay in Secret Manager)