Microsoft Copilot Mobile Proxies: QA US Features on a Carrier Line
Microsoft Copilot spans the consumer web app, the mobile apps, the Edge sidebar and Microsoft 365 surfaces, and each has features that light up by market. US availability tends to come first. For a team shipping an extension, plugin or workflow that depends on Copilot, or a QA engineer checking what a US customer on a phone experiences, the test must come from a US mobile network. A Mobile Proxies US line is one SIM in one device in a US metro, with endpoints and rotation exposed in an API, so that test can be scripted and repeated.
What varies by market and device
Feature availability by market: image generation modes, voice, shopping and some agent features appear for US accounts earlier. Bing-backed answers carry US sources, US prices and US local results for US askers. The mobile apps check platform and region before enabling features and before showing some sign-in paths. The Edge sidebar version adapts to the browser's locale and the apparent location.
A datacenter address lands in a different path: more challenges, fewer consumer features, a generic region. The carrier line lands in the ordinary consumer path because it is an ordinary consumer address shared with real subscribers.
Testing your own Copilot-dependent product
If you build a plugin, a connector or an app that relies on Copilot, the API side belongs on your server and your cloud address. The user side, where a person on a phone in Houston opens your product and Copilot behaves one way or another, belongs on the line. Put a browser profile or an emulator behind the line and run the acceptance suite there.
Pick 5G if the suite is heavy on media; 4G is adequate for text flows. Both are the same device class and the same address class. network_tier in GET /proxies/my tells your harness which is which.
Reproducing a mobile-user report
A user on Verizon in Phoenix reports that a Copilot feature inside your product does not appear. The fastest reproduction is a Verizon line in Phoenix, your product on an emulator behind its SOCKS5 endpoint, the same account type, the same steps. If it reproduces, you have the carrier and the metro in the log. If not, rotate once and try again, then try a different carrier.
Eight metros and three carriers cover the common cases. Moving a line between metros is free and keeps the remaining time, so a reproduction that needs two geographies does not need two purchases.
Matching Entra sign-in logs to the line
In a Microsoft 365 tenant, the Entra sign-in log records the source IP of every Copilot session, and Conditional Access can treat addresses outside your named locations differently. A carrier address will sit outside them. That is the point of the test: it shows what a field employee on a phone meets. Pull GET /proxies/UUID/ip-history and join new_public_ip and created_at against the sign-in log, so each policy result is tied to one carrier address. For personal accounts, the recent activity page on the Microsoft account gives a rougher version of the same join.
Rotation and acceptable use
Rotate between runs with a GET on the line's rotation_link and wait for the exit IP to change before the next run. Avoid rotating during a signed-in session; Microsoft's account protection treats an address change mid-session as a risk signal, which is correct and is also noise in your test.
Use your own Microsoft accounts and your own tenant within Microsoft's terms. The line shows you the US mobile experience; it does not change licensing, region settings on the account or any entitlement.
Setting up a Microsoft Copilot proxy on Mobile Proxies US
- Buy a line on the carrier a report came from, or on any carrier for a general US check.
- Read endpoints and credentials from the API; keep them in your harness, not in source.
- Configure a browser profile or emulator with the line and confirm the exit address is a carrier ASN.
- Run the Copilot acceptance suite or the reproduction steps; log exit IP, carrier and metro per case.
- Rotate between runs; move the line to another metro for free when geography is the variable.
Microsoft Copilot proxy questions
Will a US carrier address change my account's region?
No. Region is an account and tenant setting. The line shows what a US mobile user with your account type sees from a US network.
Which surface should I test through the line?
Whichever your users use: the web app in a browser profile, the mobile app in an emulator behind SOCKS5, or the Edge sidebar in a profile browser.
Can I automate this?
Yes. The line's endpoints, exit IP and rotation are in the API. Drive the browser with Playwright or the emulator with your usual tooling.
Is there a data meter?
No. Plans have no gigabyte counter. Very heavy daily transfer falls under a published fair-use rule; test suites are nowhere near it.
