Fix Azure-Bing Ads Auth
Budget: $10 – $50 USD
I need someone who has already integrated a SaaS platform with Microsoft Advertising (Bing Ads) through an Azure-registered application and can jump straight into resolving our authentication roadblock.
The situation
• The Azure AD app exists and should be correctly configured, yet our calls to the Bing Ads API fail at the auth step.
• We are using standard OAuth2 flows and the Microsoft Advertising SDK, but tokens are not being accepted downstream.
• All tenant-level permissions that look relevant have been granted, so I suspect a subtle setting, scope, or consent mismatch rather than a coding bug.
What I’d like from you
1. Review the current Azure AD app registration, API permissions, and redirect settings.
2. Trace the exact OAuth handshake (request, consent, token, refresh) and pinpoint the break.
3. Implement the fix—whether that’s adjusting Azure scopes, updating app registration settings, or revising our token-handling logic.
4. Prove it works by retrieving an ad account via the API from my machine or a shared test environment.
Acceptance criteria
• A clean, repeatable authentication flow that returns valid access and refresh tokens.
• Successful test call to GetCustomerAccounts (or similar) without manual intervention.
• A concise hand-off note outlining any configuration changes made in Azure AD and the final code snippet or Postman collection used for validation.
If you haven’t tackled this exact Azure + Bing Ads combo before, this project isn’t a fit. Otherwise, I’m ready to give you access and move quickly.
The situation
• The Azure AD app exists and should be correctly configured, yet our calls to the Bing Ads API fail at the auth step.
• We are using standard OAuth2 flows and the Microsoft Advertising SDK, but tokens are not being accepted downstream.
• All tenant-level permissions that look relevant have been granted, so I suspect a subtle setting, scope, or consent mismatch rather than a coding bug.
What I’d like from you
1. Review the current Azure AD app registration, API permissions, and redirect settings.
2. Trace the exact OAuth handshake (request, consent, token, refresh) and pinpoint the break.
3. Implement the fix—whether that’s adjusting Azure scopes, updating app registration settings, or revising our token-handling logic.
4. Prove it works by retrieving an ad account via the API from my machine or a shared test environment.
Acceptance criteria
• A clean, repeatable authentication flow that returns valid access and refresh tokens.
• Successful test call to GetCustomerAccounts (or similar) without manual intervention.
• A concise hand-off note outlining any configuration changes made in Azure AD and the final code snippet or Postman collection used for validation.
If you haven’t tackled this exact Azure + Bing Ads combo before, this project isn’t a fit. Otherwise, I’m ready to give you access and move quickly.