The CLI handles this complexity for you, enabling you to concentrate on your script logic without having to handle the authentication requirements for each workload as this is managed behind the scenes for you. It is becoming more and more common that you need to manage and provision assets in many different workloads in the same script and it is inconvenient to connect/disconnect with them individually. The CLI also provides a single unified login to Office 365 workloads. The Office 365 CLI is a cross-platform command line interface that enables you to manage your Office 365 tenant on any operating system or shell, whether you are on Windows, MacOS, or Linux, or use CMD, PowerShell, bash or zsh. For non-Windows users to handle such a scenario, it is common for them to use Windows Virtual Machines just to manage these settings, which is not convenient and can be costly. It is typically for developers and administrators to use a combination of different PowerShell modules to achieve this, such as PnP PowerShell and SharePoint Management Shell. Unfortunately, managing many of the workload settings is possible only through using PowerShell on Windows. Developers and administrators are no longer constrained to Microsoft development technologies tied to the Windows platform, opening up the possibility to develop applications and automation scripts using cross platform technologies to authenticate and communicate with Office 365 workloads. Why would I want to use the Office 365 CLI?Īs more and more organizations move into Office 365, more solutions are being built that expand beyond the Windows operating system. In this post, we will show you how to get started with using the Office 365 CLI with the popular PowerShell scripting language on Windows and now also cross platform using PowerShell Core ( pwsh).
0 kommentar(er)
