We need to use Get-CsOnlineApplicationInstance for one of our unattended scripts. Many of our customers have asked us to move from user based authentication to application authentication. However, Get-CsOnlineApplicationInstance will not work with application authentication.
https://learn.microsoft.com/en-us/MicrosoftTeams/teams-powershell-application-authentication#cmdlets-supported
Please support the use of Get-CsOnlineApplicationInstance with application authentication.
6 Comments
Please add support for xxx-CsOnlineApplicationInstance to Graph API or provide another solution/workaround so that scripts using application-based authentication can create and configure Call Queue and Auto-Attendants
We have been following this topic since more than a year and half and there is still no work done by MS to support app based authentication for xxx-CsOnlineApplicationInstance
Second this. With the upcoming MFA enforcement by MS we can no longer rely on a service user (with Hybrid Joined/compliant Conditional access rule). Application based authentication is then the only option left which doesn't allow this command or any other xxx-CsOnlineApplicationInstance.
MS keeps decomissioning/breaking things without suitable replacements being prepared.
The only way I still can think of is re-suing an interactive browser authentication token and re-authenticating once in a while. Sounds like a recipe for issues as it is not meant to be used that way.
Or we can create a pool of accounts this is in standby, which is a mess as we can't use our standard namingconvention at creation time. Still also wouldn't allow us to set up a checking/monitoring setup for the already created ones.You can vote for this feature on Teams Feedback: https://feedbackportal.microsoft.com/feedback/idea/9dd110cf-5940-ef11-b4ad-000d3a7aba8b
Also asked this in https://techcommunity.microsoft.com/t5/teams-developer/teams-powershell-module-get-set-new-sync/m-p/4176293#M10321, is there a ETA?
Is this something that is planned?
And if so, what's the horizon?
