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.
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, Ge...