MSTeams PowerShell Module - Expected behavior?

[Ali Salih]

Hi, 

I cross-posted this question to Twitter for responses as well. Global Admin getting this "access denied" doesn't make much sense to me, looking for additional responses. As I mentioned, this is with my Global Admin account and it is not licensed, and in many real-life use cases, these privileged accounts do not get licensed while handling administrative duties as in SPO/ODFB/Exchange etc.

https://twitter.com/alisalih/status/1052646355154464768?s=20

[#2]

I know there were some issues they upgraded the powershell module to 0.95 so be aware you have the latest Powershell module.

[#3]

Works just fine here with unlicensed GA account.

[#4]

Yes, I made sure that's the case. It is definitely 0.9.5

[#5]

@Vasil Michev That's quite interesting, can you make sure you don't have a license on the GA account for me? The reason I ask you to do that is; The program manager has confirmed the behavior and asked me to enter a uservoice entry for it, which I did.

https://microsoftteams.uservoice.com/forums/555103-public/suggestions/35756989-non-licensed-global-a...

[#6]

Well I might be getting old, but I'm not blind yet :)

Let me check directly with the powers that be.

[#7]

@Vasil Michev replying here as well since I'm also the person on twitter.  Requiring a license is an API requirement so this is technically by design - we should have been enforcing it via PowerShell as well.  There are two things that are happening in motion:

1. Evaluating whether we should remove this restriction for admins due to the great feedback here and in other forums

2. Investigating the inconsistent enforcement that you described here.

[#8]

Right, thanks :) I can tell you that a license requirement will not go well with any large organization, with very few exceptions all admin functionalities across M365 do not require license. Should you decide to enforce such requirement, please make sure to communicate this well in advance!

[#9]

+1 on what Vasil mentioned.

@Isabella Lubin - After Vasil's note that his GA account without a license can run the cmdlet, I double checked everything.

• Clean install of 0.9.5 - Check
• Verified no-license in Admin Center - Check
• Re-run the cmdlet and generated the error - Check

If needed, I can provide a Correlation ID as well to help troubleshoot the discrepancy. Just let me know. 

Thanks @Isabella Lubin and Thanks @Vasil Michev 

[#10 · Accepted solution]

The new version of the module seems to address the license requirement behavior. https://office365itpros.com/2018/11/30/teams-upgrades-powershell-module-to-0-9-6/