search

microsoft / csapps-msteams-watercooler

Water Cooler is a custom Teams app that enables corporate teams to create, invite, and join casual conversations among teammates, like those that take place by the Water Cooler or break room. Use this template for multiple scenarios, such as new non-project related announcements, topics of interest, current events, or conversations about hobbies. The app provides an easy interface for anyone to find an existing conversation or start a new one. It's a foundation for building custom targeted communication capabilities, promoting interaction amongst coworkers who may otherwise not get a chance to socialize during breaks.
MIT License
23 stars 17 forks source link

Issues giving policy to admin user #30

Closed Mani-Siga closed 2 years ago

Mani-Siga commented 3 years ago

I'm following the exact steps as outlined in the deployment guide. When I try to give the policy to admin user from section 5, I run into an error.

PS /home/mani> New-CsApplicationAccessPolicy -Identity OnlineMeeting-WaterCooler -AppIds "5b3dadaa-0982-462a-8dab-xxxxxxxxx" -Description "Water cooler - Online meeting policy"
Get-CsOnlineSession: /usr/local/share/powershell/Modules/MicrosoftTeams/2.3.1/netcoreapp3.1/SfBORemotePowershellModule.psm1:63
Line |
  63 |      $remoteSession = & (Get-CsOnlineSessionCommand)
     |                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Connecting to remote server
     | api.interfaces.records.teams.microsoft.com failed with the
     | following error message : Client did not get proper response from
     | server. For more information, see the about_Remote_Troubleshooting
     | Help topic.

Invoke-Command: /usr/local/share/powershell/Modules/MicrosoftTeams/2.3.1/netcoreapp3.1/SfBORemotePowershellModule.psm1:22959
 Line |
22959 |  …    -Session (Get-PSImplicitRemotingSession -CommandName 'New-CsApplic …
      |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      | Cannot validate argument on parameter 'Session'. The argument is
      | null or empty. Provide an argument that is not null or empty, and
      | then try the command again.

I verified that the MSTeams module version is 2.3.1, and I have tried multiple accounts to see if this is really had to do with my access issues in the Org structure. It turns out others were facing similar issues, without any solution.

This is blocking me from installing the application on my teams. Any help is appreciated.

wildmanwild commented 3 years ago

Does anybody have an answer for this issue please? I've followed the same steps set out, unfortunately each time I receive the same error as if something has been depreciated or changed around the SfB online PowerShell.

rdeoburman commented 3 years ago

Try giving policy from admin account. Please make sure MSTeams modules are updated

vdesetty commented 2 years ago

Marking the issue as resolved with the details provided above. Pls feel free to revert for any further issues.