![]() ![]() One such example is the dependance on WinRM, which forced Microsoft to use the basic authentication endpoint as a workaround to facilitate OAuth/OIDC implementation. As software inevitably evolves, the reliance on old components brought other problems. Especially in large tenants, long running scripts are known to pose a challenge, and throttling controls imposed by Microsoft didn’t help either. That said, the cloud did expose some of the weaknesses of Remote PowerShell, in the form or reliability and performance issues. One can even argue that Remote PowerShell is one of the building blocks that made the cloud service possible in the first place. It is largely thanks to it that Exchange Online offers the best admin experience out of all Microsoft 365 workloads in terms of usability, breadth of operation coverage, automation capabilities, RBAC controls, auditing, and so on. Exchange Online Remote PowerShell has been around for a long time. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |