Sandbox API returns Code 105 for active personal Microsoft account

Surefire Local Sandbox 5 Reputation points
2026-07-22T20:17:23.79+00:00

The OAuth access token for s***********@outlook.com succeeds against production GetUser, but sandbox GetUser fails with Code 105 through both REST and SOAP.

The ID token confirms the personal MSA identity:

tid: 9188040d-6c67-4c5b-b112-36a304b66dad

preferred_username: su***********@outlook.com

The user is active and set as the primary user in the sandbox UI. Requests use the universal sandbox developer token BBD37VB98 and the documented sandbox endpoints.

Please verify and confirm that the sandbox user and customer records are active.

REST Tracking ID: 6fd53c74-8456-4a47-ae76-dd19aee46d10

SOAP Tracking ID: fd6a493a-5f93-4d39-821a-9cb717be900d

** * PII Removed ** *

Microsoft Advertising API
Microsoft Advertising API

A Microsoft API that provides programmatic access to Microsoft Advertising to manage large campaigns or to integrate your marketing with other in-house systems.

0 comments No comments

1 answer

Sort by: Most helpful
  1. MS Advertising - Marvin 160 Reputation points Microsoft External Staff Moderator
    2026-07-22T23:06:38.39+00:00

    Hello Surefire Local Sandbox,

    Thank you for using our Microsoft Advertising Learn Q&A Platform!

     Thank you for providing the details, including the REST and SOAP tracking IDs.

    Error Code 105, or InvalidCredentials, means that authentication failed because the supplied credentials are invalid for the target environment, or the related account is inactive. Based on the Microsoft Advertising API documentation, this can happen when the access token or developer token is not valid for the environment being used. For example, credentials that work in production may still return Code 105 when used against the sandbox environment.

    Since you mentioned that GetUser works in production but fails in sandbox, this appears to be specific to the sandbox environment or the sandbox user/customer association.

    Please verify the following:

    • You are using the sandbox endpoints for all API calls.
    • The OAuth token was generated using the same Microsoft account that is registered or invited in the Microsoft Advertising sandbox.
    • The sandbox user has access to the intended sandbox customer/account.
    • The sandbox customer and account are active and fully set up in the sandbox UI.

    For reference, you may review the following Microsoft Advertising API resources:

    If the issue continues after confirming the items above, this may require additional review of the sandbox records associated with your Microsoft account, customer, and account, thus I’ve sent you a private message requesting additional information.

    Our support teams are pleased to engage in more in-depth discussions about your account through phone, chat, or email to offer review assistance, please see our support page to reach out!

    I trust that the details shared here will partially address your inquiry. Should you have any further questions, feel free to contact our support or reply to my private message.

     

    Kind regards, 

    Marvin | Microsoft Advertising Support Specialist | 800-518-5689 

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.