Microsoft Ads Destination Fails Due to Expired or Redeemed OAuth Token

Overview

An orchestration using the Microsoft Ads destination may fail with an error indicating that the refresh token has expired or that the authorization link has already been redeemed.

This article explains:

* Why this error occurs
* What the common error messages mean
* Step-by-step instructions to refresh or reconnect Microsoft Ads credentials in Amperity without opening a support ticket


Common Error Messages

You may see one or more of the following errors:

* “Your Microsoft Ads refresh token has expired. Please, create a new credential.”
* “Error processing authorization request: authorization_link_redeemed”

Why This Happens

* Microsoft Ads OAuth refresh tokens can expire or become invalid
* OAuth authorization links are single-use and may expire if reused
* Multiple credentials may get created unintentionally during re-authorization
* The destination may still be pointing to an older or inactive credential

⚠️ This issue is not caused by missing permissions if the user is already a Microsoft Ads Super Admin.



Prerequisites

Before proceeding, ensure:

* You have Super Admin (or equivalent) access in Microsoft Ads
* You have access to the Amperity tenant where the destination is configured
 


Step-by-Step Resolution

Step 1: Check Existing Microsoft Ads Credentials

1. Log in to your Amperity tenant
2. Navigate to: Settings → Credentials
3. Look for Microsoft Ads credentials
4. Check the Created Date

  * You may see multiple credentials created recently

If new credentials already exist, you do NOT need to generate a new OAuth link again.


Step 2: Rename the Newly Created Credentials (Recommended)

Renaming helps identify the correct credential.

1. Click on each recently created Microsoft Ads credential
2. Rename it using a clear format, for example:

  * `Microsoft Ads – Sep 17 – Primary`
  * `Microsoft Ads – Backup`

Step 3: Reconnect the Destination Using an Existing Credential

1. Navigate to: Destinations
2. Click Add Destination
3. Select Microsoft Ads as the plugin
4. In the Credential dropdown: Select one of the renamed, recently created credentials
5. Save the destination


Step 4: Validate the Orchestration

1. Go to Orchestrations
2. Locate the affected orchestration group
3. Run or wait for the next scheduled run
4. Confirm the run completes successfully without errors
 


 If You See “authorization_link_redeemed”

This means:

* The OAuth link was already used once
* Or the link has expired

Action to take:

* Do not reuse the same OAuth link
* Use one of the credentials already created
* Re-attach it via Destinations → Add Destination
 


When to Generate a New OAuth Link

Only generate a new OAuth link if:

* No Microsoft Ads credentials exist in Settings → Credentials
* All existing credentials are invalid or deleted

 OAuth links are time-bound and single-use



Final Outcome

Once the correct credential is selected and reconnected:

* Microsoft Ads destination resumes successfully
* Orchestrations run without token errors
* No further action is required

 

Still Facing Issues?

If the problem persists after following all steps:

* Verify the destination is using the correct credential
* Confirm no duplicate destinations exist
* Contact Amperity Support with:

 * Orchestration name
 * Destination name
 * Timestamp of the failure