MicrosoftTeams Powershell Library - applicationaccesspolicy cmdlets do not exist

Question

MicrosoftTeams Powershell Library - applicationaccesspolicy cmdlets do not exist

Lindsey Lanier 96

There is a lot of great documentation on available powershell cmdlets for granting access to online meetings on behalf of a user (https://learn.microsoft.com/en-us/graph/cloud-communication-online-meeting-application-access-policy). The problem is, none of these cmdlets actually exist in the PS libraries.

I have been going around in circles trying to get an answer on this issue, can someone please respond?

https://github.com/microsoftgraph/microsoft-graph-docs/issues/10911
https://stackoverflow.com/questions/65131672/allow-applications-to-access-online-meetings-on-behalf-of-a-user
https://github.com/MicrosoftDocs/office-docs-powershell/issues/6962

0 comments

Answer accepted by question author

Lindsey Lanier 96

Thank you so much for the response. However, see the NOTE in the first link I mentioned -

"Skype for Business Online Connector is currently part of the latest Teams PowerShell module. If you're using the latest Teams PowerShell public release, you don't need to install the Skype for Business Online Connector."

If you are referring to this download, https://learn.microsoft.com/en-us/microsoftteams/teams-powershell-install, that is the one I am having issues with (cmdlets do not exist even though they should). Also important to note that the account I am using to connect is a global admin per the pre-reqs.

Is there a different module I need to try? I checked all versions.

Vasil Michev 127K Reputation points MVP Volunteer Moderator

2020-12-15T16:24:01.393+00:00
The cmdlet is not directly exposed via the module, instead much like any other SfBO PowerShell cmdlet is part of the temporary file imported when creating the remote session.

Get-Command New-CsApplicationAccessPolicy CommandType Name Version Source ----------- ---- ------- ------ Function New-CsApplicationAccessPolicy 1.0 tmp_lwgycxuq.wmw

Just tried it on a different machine with the 1.1.6 version of the "combined" MicrosoftTeams module installed, and I can see/use it just fine. Tried on a different tenant and the cmdlet is available there as well.

If you are still having issues, I'd suggest trying with a different user, or "toggling" the GA permissions on/off.

1 additional answer

Your answer

Vasil Michev 127K Reputation points MVP Volunteer Moderator

2020-12-15T16:24:01.393+00:00

The cmdlet is not directly exposed via the module, instead much like any other SfBO PowerShell cmdlet is part of the temporary file imported when creating the remote session.

Get-Command New-CsApplicationAccessPolicy CommandType Name Version Source ----------- ---- ------- ------ Function New-CsApplicationAccessPolicy 1.0 tmp_lwgycxuq.wmw

Just tried it on a different machine with the 1.1.6 version of the "combined" MicrosoftTeams module installed, and I can see/use it just fine. Tried on a different tenant and the cmdlet is available there as well.

If you are still having issues, I'd suggest trying with a different user, or "toggling" the GA permissions on/off.

Answer 1

Vasil Michev 127K MVP Volunteer Moderator

Those are Skype for Business Online PowerShell cmdlets, which is no surprise given that Teams still uses almost all of the SfB policies anyway. There's a link to download the SfBO module in the first article you linked to above, download it, connect, and you will be able to run the cmdlets.

0 comments

Share via

MicrosoftTeams Powershell Library - applicationaccesspolicy cmdlets do not exist

1 additional answer

Your answer