![\"Visual](\"https:\/\/officedevblogs.wpengine.com\/wp-content\/uploads\/2020\/05\/office365-cli-visual-studio-code-codetour.png\")
<\/a>To use the CodeTour report for upgrading your SharePoint Framework project, be sure you have the CodeTour Visual Studio Code extension<\/a> installed and then execute:<\/p>\n The next time you open your project in Visual Studio Code, the CodeTour extension will start the tour walking you through the different steps to upgrade your project.<\/p>\n The CodeTour report offers a richer upgrade experience that we hope you will like. Big thanks to Hugo Bernier for contributing this new report type and don’t hesitate to let us know if you have any feedback or ideas for improvement.<\/p>\n Next to introducing the new CodeTour SPFx project upgrade report, we have improved the project upgrade logic. While originally we’d suggest upgrading only the required dependencies, in this version we’ve extended the upgrade report to include some of the optional dependencies as well. In the future versions of the CLI, we’ll extend this list covering all When building SharePoint Framework solutions, developers can use many of the 1 million packages published on npm to speed up their development process. By default, however, these packages get included in the generated solution bundle, unnecessarily increasing its size. While you can configure them to be stored externally, it’s not always trivial to use the right way of doing it. To simplify the process of separating packages from the solution bundle, Office 365 CLI offers a command that analyzes your solution and shows you code necessary to include in your project.<\/p>\n For this version of Office 365 CLI, Vincent Biret improved the logic to detect the type of package so that the CLI can offer you more accurate suggestions for the necessary code snippets.<\/p>\n To get suggestions on how to separate the dependencies from your SPFx project, execute:<\/p>\n Office 365 CLI is a versatile tool for managing your Microsoft 365 tenant. Whether you execute a single command on your desktop or build automation scripts integrated into builds or scheduled tasks. Before you can start communicating with your tenant, you need to log in to it. And often that’s a challenge. Where do you store securely the necessary credentials?<\/p>\n To simplify using Office 365 CLI in automation scenarios, in this version we introduce support for logging in to Microsoft 365 using managed identity. If you use the CLI on a VM or Azure Function that has managed identity set up or in Azure Cloud Shell, you can use the existing identity and don’t need any separate credentials to communicate with Microsoft 365!<\/p>\n All you need to do is to log in using managed identity, by executing:<\/p>\n For more information about using managed identity with Office 365 CLI, see the documentation<\/a>. Big thanks to Velin Georgiev for contributing this new authentication method and Paul Schaeflein for assisting with the research.<\/p>\n When building solutions on Microsoft 365, chances are that you will deploy some pieces of it to Azure. For these components to be able to communicate with Microsoft 365, they need to be granted access to the specific services.<\/p>\n To help you automate configuring these permissions, Velin Georgiev contributed a command to add app role assignments to service principals.<\/p>\n For example, to allow the specified service principal to read information about SharePoint sites, execute:<\/p>\n For more information about managing Azure AD apps using the Office 365 CLI, see the documentation<\/a>.<\/p>\n Recently, during Build, Microsoft announced the preview of new Microsoft Graph APIs for managing To Dos. These APIs extend the task management capabilities of Graph that in the past allowed you to create Planner and Outlook tasks.<\/p>\n For this version of Office 365 CLI, Yannick Plenevaux contributed a command to add a To Do list. To add a To Do list using the CLI, execute:<\/p>\n While the new To Do APIs already work, they haven’t been officially released. When the API becomes officially available, you can expect us to extend the support for To Do in Office 365 CLI.<\/p>\n Microsoft Teams gained a lot of popularity lately. Many organizations have started using Teams in their daily work and are now looking into extending them to their needs to get even more out of them. A part of that is the ability to allow users to use the different applications directly from the context of Teams.<\/p>\n To help you automate the process of configuring Microsoft Teams, Aakash Bhardwaj contributed a command to add personal Teams apps.<\/p>\n To add a personal Teams app, execute:<\/p>\n For more information about managing Microsoft Teams using the Office 365 CLI, see the documentation<\/a>.<\/p>\n Organizations on Microsoft 365 have plenty of choices when it comes to how to facilitate their collaboration. They can choose the good old e-mail, but also can use services like Microsoft Teams or Yammer. Each of these services shines in one or more specific scenarios and there is no right or wrong when it comes to using them in the workplace.<\/p>\n In this release of the Office 365 CLI, we continued to extend support for Yammer. Patrick Lambert contributed commands to manage Yammer groups’ users and (un)liking messages.<\/p>\n To add the current user to a Yammer group, execute:<\/p>\n To remove the current user from a Yammer group, execute:<\/p>\n To like the specific Yammer message, execute:<\/p>\n Since Yammer is not available in all tenants, we made its permissions optional in the Azure AD app used by the Office 365 CLI. Before you can start using Yammer commands in the Office 365 CLI, you need to consent the Azure AD app access to Yammer by executing:<\/p>\n For more information about managing Yammer using the Office 365 CLI, see the documentation<\/a>.<\/p>\n Office 365 CLI contains nearly 400 commands allowing you to manage different services in Microsoft 365. Many of these commands require admin-level permissions and chances are, that you might not need to use all of them in your organization. By default, Office 365 CLI uses its own Azure AD application with all necessary permissions assigned to it. But if you want to have more control over the admin-level access in your tenant you can use your own Azure AD application instead.<\/p>\n To simplify the processing of setting up and using your own Azure AD application with Office 365 CLI, Garry Trinder contributed a detailed walkthrough<\/a> taking you step-by-step through the whole configuration process. We hope you find it helpful and please don’t hesitate to reach out to us if we can clarify or improve anything.<\/p>\n Office 365 CLI is a great tool both for quick adjustments to the configuration of your Microsoft 365 tenant as well as automating more complex tasks. Because Office 365 CLI is cross-platform you can use it on any OS and in any shell. To help you get started using the Office 365 CLI for automation scenarios, we started gathering some sample scripts. Here are the latest additions to the collection.<\/p>\n If you have any scripts that you use frequently, please share them with us<\/a> so that we can learn more about the common automation scenarios.<\/p><\/blockquote>\n When merging or migrating tenants, Microsoft 365 groups or Teams you might need to change memberships of these groups.<\/p>\n To simplify this process, Joseph Velliah contributed a sample script that allows you to add\/remove users to Microsoft Teams and Microsoft 365 groups in bulk<\/a>.<\/p>\n Tenant Wide Extensions list from the App Catalog helps to manage the activation\/deactivation of the tenant wide extensions.<\/p>\n Shantha Kumar T contributed a sample script helps to disable the specified tenant-wide extension<\/a>.<\/p>\n You’ve built an amazing new web part and now you want to programmatically add it to a modern page.<\/p>\n Yannick Plenevaux contributed a sample script that helps you add your web part to the page with your custom properties that might be dynamic according to your script<\/a>.<\/p>\n This release wouldn’t be possible without the help of (in alphabetical order) Hugo Bernier<\/a>, Aakash Bhardwaj<\/a>, Vincent Biret<\/a>, Velin Georgiev<\/a>, Shantha Kumar<\/a>, Patrick Lamber<\/a>, Waldek Mastykarz<\/a>, Aleksandar Nikoli\u0107<\/a>, Yannick Plenevaux<\/a>, Paul Schaeflein<\/a>, Albert-Jan Schot<\/a>, Pete Skelly<\/a>, Garry Trinder<\/a> and Joseph Velliah<\/a>. Thank you all for the time you chose to spend on the Office 365 CLI and your help to advance it!<\/p>\n Here are some things that we’re currently working on.<\/p>\n Each month we release a new version of Office 365 CLI with new features and improvements. We strive to follow semantic versioning to help you understand which versions are backward-compatible and which aren’t. Last year, we released a new major version to improve some things that couldn’t have been done in a backward-compatible way. Right now, we’re starting planning another major release that will help us clean up Office 365 CLI from obsolete features and prepare it for at least the next year.<\/p>\n The most noteworthy changes are renaming Office 365 CLI<\/em> to Microsoft 365 CLI<\/em> to align with Microsoft’s marketing and removing the immersive mode which could allow us to modernize CLIs engine in the near future.<\/p>\n We’ll start the work on v3 of Office 365 CLI shortly and will keep you updated as we introduce new changes for you to try. Stay tuned!<\/p>\n Microsoft 365 is evolving and new capabilities are being released every day. With the Office 365 CLI, we aim to help you manage your tenant on any platform in a consistent way, no matter which part of Microsoft 365 you interact with. While we keep adding new commands to the Office 365 CLI each release, we still barely scratched the surface with what’s possible in Microsoft 365. In the upcoming versions of the Office 365 CLI, you can expect us to add more commands across the different workloads in Microsoft 365.<\/p>\n To make it easier for you to see how the CLI commands compare to the different PowerShell cmdlets, we’ve extended the comparison sheet<\/a> with cmdlets for Flow, PowerApps, and Teams.<\/p>\n In every release of the Office 365 CLI, we introduce new commands for managing Microsoft 365. With 360 commands across the different Microsoft 365 services, the Office 365 CLI has become a powerful tool, not just for managing your tenant but also for automating your daily work.<\/p>\n We’d love to show you how you can use the Office 365 CLI to build automation scripts in PowerShell Core and Bash. If you have any scripts using SPO or PnP PowerShell that you use frequently, please share them with us<\/a> so that we can learn more about the common automation scenarios.<\/p>\n Currently, Office 365 CLI has dedicated commands for retrieving, creating, and updating resources. If you were to create a script that ensures a specific configuration, for each resource you’d need to see if it exists, create it if it doesn’t, or update it if it does.<\/p>\n We’re thinking about simplifying this scenario by introducing commands with a new verb named We’ll start to implement this idea<\/a> on the At this moment, the most of SharePoint We’re thinking about addressing this limitation by allowing you to set the value of any property exposed on the SharePoint object. This would work only for properties that have values of simple types like We would offer rudimentary logic of checking if the specified properties are valid, by examining the latest version of the SPO CSOM assemblies and checking which properties on the particular SharePoint class have setters and values of the supported types and thus can be used.<\/p>\n What do you think of this approach? Would this help to solve a problem you have? In the previous release, we have extended the Get the latest release of the Office 365 CLI from npm by executing in the command line:<\/p>\n If you need more help getting started or want more details about the commands, the architecture, or the project, go to aka.ms\/o365cli<\/a>. If you see any room for improvement, please, don’t hesitate to reach out to us either on GitHub<\/a> or twitter<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" We’ve just published a new version of the Office 365 CLI with commands for managing Office 365 tenants and SharePoint Framework projects on any platform.<\/p>\n","protected":false},"author":69079,"featured_media":25159,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[128,11],"tags":[53,140,19],"class_list":["post-4737","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-teams","category-office-add-ins","tag-office-365","tag-office-365-cli","tag-sharepoint-framework"],"acf":[],"blog_post_summary":" We’ve just published a new version of the Office 365 CLI with commands for managing Office 365 tenants and SharePoint Framework projects on any platform.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/4737","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/69079"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=4737"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/4737\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/25159"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=4737"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=4737"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=4737"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}o365 spfx project upgrade -o<\/span> tour\n<\/code><\/pre>\n<\/div>\n<\/div>\nImproved SPFx project upgrade<\/h3>\n
@microsoft<\/code> dependencies that are a part of the SharePoint Framework. We’ve also improved the accuracy of our findings which should streamline the upgrade process.<\/p>\nImproved externalizing SPFx project dependencies<\/h3>\n
o365 spfx project externalize\n<\/code><\/pre>\n<\/div>\n<\/div>\nAdded support for logging in using managed identity<\/h3>\n
o365 login --authType<\/span> identity\n<\/code><\/pre>\n<\/div>\n<\/div>\nAdd Azure AD app role assignments<\/h3>\n
o365 aad approleassignment add --appId<\/span> \"57907bf8-73fa-43a6-89a5-1f603e29e451\"<\/span> --resource<\/span> \"SharePoint\"<\/span> --scope<\/span> \"Sites.Read.All\"<\/span>\n<\/code><\/pre>\n<\/div>\n<\/div>\nAdd a Microsoft To Do list<\/h3>\n
o365 todo list add --name<\/span> \"My task list\"<\/span>\n<\/code><\/pre>\n<\/div>\n<\/div>\nInstall personal Teams apps<\/h3>\n
o365 teams user app add --appId<\/span> 4440558e-8c73-4597-abc7-3644a64c4bce --userId<\/span> 2609af39-7775-4f94-a3dc-0dd67657e900\n<\/code><\/pre>\n<\/div>\n<\/div>\nManage Yammer users and messages<\/h3>\n
o365 yammer group user add --id<\/span> 5611239081\n<\/code><\/pre>\n<\/div>\n<\/div>\no365 yammer group user remove --id<\/span> 5611239081\n<\/code><\/pre>\n<\/div>\n<\/div>\no365 yammer message like set<\/span> --id<\/span> 5611239081\n<\/code><\/pre>\n<\/div>\n<\/div>\nconsent --service<\/span> yammer\n<\/code><\/pre>\n<\/div>\n<\/div>\nNew user guide Using your own Azure AD identity<\/h3>\n
New script samples<\/h3>\n
Bulk add\/remove users to Microsoft Teams and Microsoft 365 Groups<\/h4>\n
Disable the specified tenant-wide extension<\/h4>\n
Add custom client-side web part to modern page<\/h4>\n
Contributors<\/h2>\n
Work in progress<\/h2>\n
CLI v3: preparing for the next major version<\/h3>\n
More commands, what else<\/h3>\n
Script examples<\/h3>\n
ensure<\/code> commands<\/h3>\nensure<\/code>. For example, to ensure that a particular site collection exists, instead of executing a combination of spo site list<\/code>\/spo site get<\/code>, spo site add<\/code> and spo site set<\/code>, you’d execute spo site ensure<\/code> with the necessary parameters which would automatically verify if the particular site exists and matches your configuration. If the site doesn’t exist, it would create it. If it does, the command would check if the properties you specified match the retrieved site and update them if necessary.<\/p>\nspo site<\/code> commands. We’d love to hear from you<\/a> if it’s something that you’d find helpful and what other objects we should take into account.<\/p>\nSetting arbitrary properties on SharePoint objects<\/h3>\n
set<\/code> commands in the Office 365 CLI support only a handful of options that correspond to the properties of their SharePoint class, like Web<\/code>, Site<\/code>, List<\/code>, etc. This is similar to how the Set-PnP*<\/code> cmdlets work. However, because PnP PowerShell works with CSOM, this limitation there is often circumvented, by retrieving the CSOM object, updating its properties, and calling $object.ExecuteQuery()<\/code> to persist the changes outside of PnP cmdlets. Because the CLI doesn’t use CSOM, this isn’t possible and users are limited to using whatever options are exposed by the CLI commands.<\/p>\nbool<\/code>, string<\/code> or int<\/code> because complex values likely can’t be serialized to string<\/code> without additional logic.<\/p>\nspo web set<\/code> command with this functionality. We’d love you to try it and tell us what you think<\/a>.<\/p>\nTry it today<\/h2>\n
npm i -g<\/span> @pnp\/office365-cli\n<\/code><\/pre>\n<\/div>\n<\/div>\n