What Microsoft H1B Employees Should Do After the Layoffs

USCIS gives you up to 60 consecutive days, or until the end of your I-94 validity (whichever is shorter), to either find a new H1B sponsor, change status, or depart the U.S. The clock starts on the last day of employment as reported by Microsoft to USCIS, not your last day in the office and not the end of any severance period.

If Microsoft offered you severance with a paid notice period or 'garden leave,' the employment-end date on your termination letter is the date that matters. Severance paid as a lump sum after employment ends does not extend your status — many people lose weeks assuming it does.

This week, do three things:

1. Email Microsoft's immigration team (usually routed through Fragomen or Berry Appleman for Microsoft) and ask in writing for: (a) your official last day of employment, (b) confirmation that Microsoft has withdrawn or will withdraw your H1B petition, and (c) the date of withdrawal. 2. Pull your most recent I-797 approval notice and your I-94 from i94.cbp.dhs.gov. Whichever expires first is your real deadline. 3. If Microsoft filed an I-140 for you and it has been approved for more than 180 days, that I-140 stays valid for priority-date retention and H1B extensions beyond the 6-year cap, even after Microsoft withdraws it. Save the I-140 receipt and approval notices to personal email immediately.

Microsoft's mainland cloud cuts are driven by regulatory pressure — the U.S. tightening export controls on advanced cloud/AI services to China, and China's Data Security Law and PIPL making it harder for U.S. firms to operate Azure China without a local partner (21Vianet). That has two practical consequences for laid-off H1B workers:

• **The skill set transfers, the geopolitical baggage doesn't.** Azure, Kubernetes, distributed systems, ML infra, and compliance experience are still in high demand at AWS, Google Cloud, Oracle Cloud, Databricks, Snowflake, and the AI labs. You are not competing in a shrinking market — you're competing in a reshuffled one.
• **U.S.-based cloud roles at companies that *don't* operate in China may screen you faster.** If your resume reads 'Azure China / Microsoft Research Asia,' lead with the technical stack and U.S.-facing customers you supported, not the org chart. Recruiters at export-sensitive companies (defense-adjacent, federal cloud, semiconductor) will move faster when the China exposure is contextualized rather than featured.

Don't take this as career advice to hide anything — disclose accurately on I-9, background checks, and OFCCP forms. This is about resume framing for the first 30 seconds of recruiter triage.

For someone leaving Microsoft with a strong tech resume, these are the options in roughly the order you should pursue them:

1. H1B transfer to a new employer (fastest, most common). A new employer files an H1B transfer petition; you can start work the day USCIS receives the petition (not approves it) as long as you're within the 60-day window and were in valid status. Premium processing ($2,805) gets a decision in 15 business days. Target companies that file hundreds of H1Bs annually — Amazon, Google, Meta, Apple, NVIDIA, Oracle, Salesforce, Stripe, Databricks, the big banks, and the Indian IT services firms (TCS, Infosys, Cognizant) who are typically willing to file fast.

2. H4 dependent status (if your spouse is on H1B, L1, or has a green card). Filing an I-539 within 60 days stops the clock and keeps you legally in the U.S. while you continue job hunting. If your spouse has an approved I-140, you can also get H4 EAD work authorization, though processing currently runs 4-8 months.

3. B1/B2 visitor status as a bridge. File I-539 to change to B-2 before day 60. This is a legitimate option USCIS has explicitly acknowledged for laid-off workers needing time to wind down U.S. affairs or interview. You cannot work on B-2, but the filing itself stops the unlawful-presence clock. Use this only if you can't land a transfer in time.

4. O-1 extraordinary ability. Realistic if you have patents, publications, conference talks, or were a tech lead on a widely-used product. Microsoft Research alumni often qualify. Timeline: 4-8 weeks with premium processing, plus 2-4 weeks of evidence gathering.

5. F-1 student status. Filing I-539 to change to F-1 for a Master's or second Master's is viable but slow (often 4-6 months for approval), and you can't start work on OPT until you've been enrolled for a full academic year.

6. Cap-exempt H1B at a university, nonprofit research org, or affiliated employer. No lottery required, can be filed any time of year. Microsoft Research alumni often have ties to universities that can sponsor.

Day 1-2: - Get your termination letter in writing with the exact last-day-of-employment date. - Download every immigration document Microsoft has filed for you: I-797 approvals, LCA copies, I-140 approval notice if applicable, prior H1B petitions. Microsoft's immigration portal usually has these — pull them before your access is revoked. - Forward everything to a personal email.

Day 3-5: - Update LinkedIn to 'Open to Work' (use the recruiter-only setting if you don't want it public). Post once explaining you're affected by the Microsoft cloud reorg and looking — these posts consistently generate the most inbound from recruiters. - Apply to 15-20 roles at companies that file H1B transfers routinely. Don't filter for 'sponsor H1B' on job boards — the data is unreliable. Check the H1B disclosure data at h1bgrader.com or myvisajobs.com to verify a company has actually filed transfers recently. - Email your direct manager and 5-10 closest colleagues for referrals. Internal referrals at Amazon, Google, and Meta meaningfully accelerate recruiter response.

Day 6-7: - Talk to an immigration attorney for a paid 30-minute consult ($150-300). Specifically ask: (a) when does my 60-day grace period end, (b) is my I-140 portable, (c) what's the safest backup status if I don't have an offer by day 50.

Weeks 2-3: Run the job search like a project. - Aim for 5-10 first-round interviews per week. The market for senior cloud/AI engineers is still active, but recruiters at top companies will push H1B transfers to the back of the queue if you're not assertive about the 60-day window. Tell every recruiter on the first call: 'I'm on H1B, I have until [date], I need the offer and petition filed before then.' Good recruiters will escalate. - If you have an approved I-140 older than 180 days, mention this in every conversation. It means the new employer can extend your H1B beyond the 6-year cap and your priority date ports — a real selling point.

Week 4: Decide your backup. - If you don't have an offer with a signed petition by day 45, file an I-539 to change to H-4 (if eligible) or B-2. The receipt notice keeps you in authorized stay while USCIS adjudicates. Yes, this can feel like giving up — it's not. People routinely file B-2 bridges, land offers in months 2-3, and transfer back to H1B with a new petition. - If you're going to leave the U.S., do it before day 60. Departing within the grace period preserves your ability to re-enter on a new H1B without consular delays beyond the normal stamping process.

• **Assuming severance extends the clock.** It doesn't. Last day of employment is what USCIS uses.
• **Waiting for premium-processing approval before starting.** H1B portability (AC21 §105) lets you start working the moment the new petition is *received* by USCIS, not approved. Receipt notice in hand = legal to start.
• **Letting the I-94 lapse while a change-of-status I-539 is pending.** File the I-539 *before* day 60 — the timely filing is what protects you, not the approval.
• **Not pulling the I-140 approval notice before losing Microsoft email access.** You will need this for any future H1B extension. Microsoft will not be helpful retrieving it six months later.
• **Taking unpaid 'consulting' work during the grace period.** You are not work-authorized during the grace period. Any paid work, even contract, requires a new H1B petition to be filed first.
• **Self-deporting too early.** The 60 days is yours. Don't book a flight on day 20 because a recruiter ghosted you on day 18.

Microsoft transfers many engineers into the U.S. on L1A or L1B. The 60-day grace period applies to L1 holders too, but L1-to-H1B transfers are harder because they require a fresh H1B petition subject to the cap — unless the new employer is cap-exempt or you've previously been counted against the H1B cap. If you're L1B and unsure, ask an attorney about your prior H1B history; many L1 holders forget they were on H1B before and are still cap-counted, which makes the transfer fast.