What is Teams Pro? A look at the latest M365 service plan

Microsoft announced a Teams Pro service plan on Feb 9, 2021. This service plan will be rolled out for all customers with applicable SKUs (Office 365 E5/E3/A5/A3, and Microsoft 365 Business Standard/Business Premium licenses) at no additional cost. You can read the message center announcement in your admin center.

What features are included in Teams Pro?

Teams Pro will include a set of features that will enable “meeting intelligence” and webinar capabilities. While nothing has currently been officially announced, I speculate the new custom registration pages will be included in the Teams Pro feature set.

Admins will be able to turn Teams Pro functionality/capabilities on or off for users similar to how they currently can toggle any app/service product license assignment on/off for users.

How does Teams Pro change my current Teams licensing and M365 cost?

This new addition will not change existing licenses, and will not come at an additional cost to those with Office 365 E5/E3/A5/A3, and Microsoft 365 Business Standard/Business Premium licenses.

When is Teams Pro available?

Teams Pro will be showing up mid-March 2021.

“We’ve run into a problem with your Office 365 subscription” solution

I recently moved from one tenant to another and even though I’d signed out of my client Office applications and signed in with my new tenant, I was still getting this error message when opening any Office app.

“We’ve run into a problem with your Office 365 subscription, and we need your help to fix it.”

“Go to My Account” wasn’t an option, as that account no longer existed. “Remind Me Later” only delays the inevitable temper tantrum you know must be coming.

Thankfully, there were two great posts out there that helped me solve this by removing the product keys associated with the de-activated license via command prompt. Just two notes before you begin:

  1. Make sure you run PS/Command prompt as administrator (right-click command prompt, run as administrator).
  2. Your path to the OSPP.VBS file might be different than what’s in their posts. For example, mine was actually located here: C:\Program Files\Microsoft Office\Office16\OSPP.VBS