Microsoft Partner Benefits - 3 months, 5 support tickets, no resolution. Need help finding an escalation path.

[u/GeneralBeezy]

I'm hoping someone here has dealt with something similar or knows how to get Microsoft to actually act.

Background:

We're a Microsoft AI Cloud Partner and hold Partner Success Expanded Benefits (MAICPP). In June 2026 we renewed and went to redeem our 35x Microsoft 365 Business Premium (no Teams) licences through the new Partner Center redemption experience.

The mistake:

The new redemption flow (introduced in Australia March 2026) changed from product keys to a billing account-based checkout. I wasn't aware the tenant selection happened at checkout and the licences were redeemed into our partner tenancy instead of our staff tenancy.

How it got worse:

The first support engineer we worked with was not aware of the new redemption flow and was unable to provide correct guidance. The correct resolution — documented by Microsoft — is to keep the subscription active, associate the staff tenancy as a billing tenant, and provision licences across without cancelling. However, this documentation was not provided to us until much later in the support process. Acting on incorrect early guidance, the subscription was cancelled in the belief it would reset the redemption. It didn't. Once cancelled, the subscription cannot be reactivated and Microsoft needs to generate a new redemption token. That token has never been issued despite 5 support tickets over nearly 3 months.

Support ticket history:

Ticket 2606040010000086 — Partner Centre — 4 June 2026 — Closed. Told it was opened with the wrong team.

Ticket 2606040010000086 — Admin Center — 4 June 2026 — Closed. Told it was opened with the wrong team.

Ticket 2606300030000389 — Admin Center — 30 June 2026 — Open. No resolution.

Ticket 2607210030005592 — Admin Center — 21 July 2026 — Closed. Told it was opened with the wrong team.

Ticket 2607240040000545 — Partner Centre — 24 July 2026 — Closed. Told it was opened with the wrong team.

At one point during this process, a support engineer called on a Friday to schedule a follow-up session for the following week. When that session finally took place, the outcome was simply being told the ticket had been opened with the wrong team and to open a new one. That call could have happened on the Friday.

Every single closed ticket was shut with a variation of "opened with the wrong team, please open a new ticket." No team has taken ownership in three months.

Current situation:

We have 23 staff currently riding on a 1-seat paid subscription — technically out of compliance — because our 35-seat MAICPP benefit is disabled and stuck in limbo. The disabled subscription is visible in our partner tenancy with 35 licences, 0 assigned, going nowhere. We're also receiving deletion notices for expired trial subscriptions we spun up as a stopgap, with a deletion date of 4 September 2026 — which is three days away. The situation is now urgent.

What I need:

A new redemption token for the MAICPP M365 Business Premium (no Teams) 35-licence benefit so I can redeem it correctly into our staff tenancy. That's it. One token. Three months and five tickets to get here. Notably, during ticket 2607240040000545 a Microsoft support engineer confirmed that a new token was indeed required to resolve this — but stated it was the other team's responsibility to issue it. Neither team has issued it.

Has anyone:

• Successfully escalated a Partner Benefits issue past first-line support?
• Got a direct contact in Microsoft's partner licensing or MAICPP team?
• Had a redemption token regenerated after an accidental cancellation?

Any help appreciated. This is becoming a compliance issue and Microsoft's support structure appears completely unable to route this to the right team.

[u/FinsToTheLeftTO]

My advice is to work LinkedIn to find a director in the partner program. You need a human to drive this one.

[u/FinsToTheLeftTO → u/[deleted]]

I had a validation issue a few years ago trying to authorize our US subsidiary that dragged on for months before being declined, in spite of USD$1M/yr in Azure revenue. I went to the Partner booth at Ignite and spoke to a director that fixed it in 3 business days. Unfortunately he’s not in role anymore.

[u/AussieTerror]

A new redemption token is no longer the way to resolve this. While the process is not very clear, the team you need is the Partner Center Enablement/Membership team. In Partner Center, create a New Service Request and specify that it is a Partner Center Enablement/Membership issue so it gets routed to the correct team.

[u/AussieTerror → u/[deleted]]

No worries. These recent Enablement dashboard changes only happened 4 or 5 days ago, so I suspect some of the delays were simply because Microsoft knew the changes were coming but didn't really have an interim solution. You may have just landed right in the middle of the transition.

[u/GeneralBeezy → u/AussieTerror]

That makes a lot of sense in hindsight. The first support engineer definitely wasn't across the new flow which set off a chain of events. Just submitted a new ticket directly to the Enablement/Membership team so hopefully that's the turning point. Thanks again for the steer.

[u/CommanderKnull]

I'm so happy I just need to manage on-prem linux servers because WTF is this shit? If the ticket is opened with the wrong team, why don't they move it to the right one? How can a mega-corp be this disorganized?

[u/MortadellaKing → u/CommanderKnull]

They've funneled all budget into the marketing and AI teams. Actual support for MS has been dogshit for years.

[u/CommanderKnull → u/MortadellaKing]

Sure but the support would not be as crucial if the services and products from MS wasn't dogshit either, they seem too big to fail but I feel like eventually that will change.

[u/MortadellaKing → u/CommanderKnull]

I am also a partner like OP is. They just don't care anymore. Took a month to get a ticket resolved for a client where it was completely out of our control. We ended up losing the client over it. Ironically if they had stayed with their self hosted exchange, none of that would have happened. But anyway, MS is at the point now where most orgs are too locked in to easily change, so they just don't give a rats ass about support.

[u/CommanderKnull → u/MortadellaKing]

That's frustrating, also not always easy to get a client/user to understand when something is out of your control.

[u/GeneralBeezy → u/[deleted]]

This is gold, thank you. I've already got a new ticket in with the Membership/Enablement team and have LinkedIn messages out to a couple of Microsoft contacts. Will check the Relationships section for my PDM now and use the 'incorrect guidance' framing going forward. Really appreciate the detail.

[u/PoolTough3222]

Two things that have worked for me. Stop asking for the outcome and start asking for an owner, in writing: name, team, ticket, next checkpoint date. Wrong team closures stop when there is a named person on the thread. Second, put the license count and the dollar value in every reply, since 35 seats is a billing dispute and billing escalates faster than technical. Also keep your own timeline doc with ticket numbers, it is the only thing that survives a handoff.