Managing permissions and login credentials to access Microsoft Advertising accounts
The sandbox environment is separate from production and has its own set of supported endpoints and credentials. The correct entry point for working with Microsoft Advertising sandbox today is the secure sandbox URL, not the sandbox.bingads.microsoft.com host that is returning 404 and a mismatched certificate.
Use these endpoints and steps instead:
- Sign up and sign in to sandbox
- Go to the Microsoft Advertising secure sandbox site:
https://secure.sandbox.bingads.microsoft.com/(from the Sandbox and Get Started guides). - Create or use a sandbox customer as described under Initial Customer Sign Up:
- Either:
- Create a Microsoft account (MSA) with an
outlook.comemail address and complete the Create Account flow, or - Use Sign up with Google and complete the Google OAuth flow.
- Create a Microsoft account (MSA) with an
- On the Create Account form, choose Skip payment information for Go Live.
- Either:
- Go to the Microsoft Advertising secure sandbox site:
- If an outlook.com MSA is needed for OAuth
- If the sandbox customer was created with an
outlook-int.comor other non‑outlook domain, invite anoutlook.comuser from within the sandbox UI:- In the sandbox UI, go to Settings → User management → Invite user.
- Enter an
outlook.comemail only (other domains will remain in “pending” and never send). - The invited user follows the email link, creates an MSA with an
outlook.comaddress if needed, then signs back in athttps://secure.sandbox.bingads.microsoft.com/.
- If the sandbox customer was created with an
- Get API access for sandbox
- Use the sandbox‑specific credentials and helpers:
- Universal sandbox developer token:
BBD37VB98. - Own application ID (client ID) is still required; for C# samples, the public “Tutorial Sample App” client ID
00001111-aaaa-2222-bbbb-3333cccc4444can be used in sandbox.
- Universal sandbox developer token:
- OAuth endpoint remains
login.microsoftonline.com, but tokens and calls must target sandbox web service addresses.
- Use the sandbox‑specific credentials and helpers:
- Best practices and limitations
- Sandbox and production use separate credentials and WSDL/web service addresses.
- Sandbox capacity is lower; do not use it for stress or capacity testing and avoid more than one thread.
- If the 404/SSL issue persists
- Since sandbox may be down for maintenance with or without notice, or there may be a transient configuration issue on that legacy host, use the secure sandbox URL and API endpoints documented in the Sandbox and Get Started guides.
- For persistent access issues or if the secure sandbox URL also fails, raise the problem via Microsoft Q&A (tag
advertising-api) or contact Microsoft Advertising Support, providing environment details and exact URLs used.
References: