@pnp/cli-microsoft365 11.7.0-beta.b9f508d → 11.7.0-beta.bd906c5

package/docs/docs/cmd/exo/approleassignment/approleassignment-add.mdx

@@ -65,6 +65,25 @@ To use this command you must be at least **Privileged Role Administrator**.
 
 :::
 
+## Permissions
+
+<Tabs>
+  <TabItem value="Delegated">
+
+  | Resource        | Permissions                  |
+  |-----------------|------------------------------|
+  | Microsoft Graph | RoleManagement.ReadWrite.Exchange |
+
+  </TabItem>
+  <TabItem value="Application">
+
+  | Resource        | Permissions                  |
+  |-----------------|------------------------------|
+  | Microsoft Graph | RoleManagement.ReadWrite.Exchange |
+
+  </TabItem>
+</Tabs>
+
 ## Examples
 
 Assign a role specified by id to a service principal specified by id and scope the assignment to the whole tenant

package/docs/docs/cmd/file/convert/convert-pdf.mdx

@@ -1,4 +1,6 @@
 import Global from '../../_global.mdx';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
 
 # file convert pdf
 
@@ -30,6 +32,25 @@ If you choose to store the converted file in a document library, CLI will store
 
 If the conversion process fails, CLI will attempt to clean up the temporary files (the source file uploaded to your tenant, if you're converting a local file to PDF, and the converted PDF file on your disk if you chose to upload the converted file to your tenant). If removing the temporary files fails, you will need to clean them up yourself. CLI will list the URL and/or path of the files to remove.
 
+## Permissions
+
+<Tabs>
+  <TabItem value="Delegated">
+
+  | Resource        | Permissions                     |
+  |-----------------|---------------------------------|
+  | Microsoft Graph | Files.ReadWrite, Sites.Read.All |
+
+  </TabItem>
+  <TabItem value="Application">
+
+  | Resource        | Permissions                         |
+  |-----------------|-------------------------------------|
+  | Microsoft Graph | Files.ReadWrite.All, Sites.Read.All |
+
+  </TabItem>
+</Tabs>
+
 ## Examples
 
 Converts local file to PDF and stores the converted file on the disk

package/docs/docs/cmd/file/file-add.mdx

@@ -1,4 +1,6 @@
 import Global from '../_global.mdx';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
 
 # file add
 
@@ -31,6 +33,25 @@ The `folderUrl` must be an absolute URL to the document library where the file s
 
 By default, the `file add` command will automatically lookup the ID of the site where you want to upload the file based on the specified `folderUrl`. It will do this, by breaking the URL into chunks and incrementally calling Microsoft Graph to retrieve site information. This is necessary, because there is no other way looking at the URL to distinguish where the site URL ends and the document library URL starts. If you want to speed up uploading files, or you use resource-specific consent and your Microsoft Entra app only has access to the specific site, you can use the `siteUrl` option to specify the URL of the site yourself.
 
+## Permissions
+
+<Tabs>
+  <TabItem value="Delegated">
+
+  | Resource        | Permissions                      |
+  |-----------------|----------------------------------|
+  | Microsoft Graph | Files.ReadWrite, Sites.ReadWrite.All |
+
+  </TabItem>
+  <TabItem value="Application">
+
+  | Resource        | Permissions         |
+  |-----------------|---------------------|
+  | Microsoft Graph | Sites.ReadWrite.All |
+
+  </TabItem>
+</Tabs>
+
 ## Examples
 
 Uploads file from the current folder to the root folder of a document library in the root site collection

package/docs/docs/cmd/file/file-copy.mdx

@@ -1,4 +1,6 @@
 import Global from '../_global.mdx';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
 
 # file copy
 
@@ -31,6 +33,25 @@ m365 file copy [options]
 
 <Global />
 
+## Permissions
+
+<Tabs>
+  <TabItem value="Delegated">
+
+  | Resource        | Permissions         |
+  |-----------------|---------------------|
+  | Microsoft Graph | Sites.ReadWrite.All |
+
+  </TabItem>
+  <TabItem value="Application">
+
+  | Resource        | Permissions         |
+  |-----------------|---------------------|
+  | Microsoft Graph | Sites.ReadWrite.All |
+
+  </TabItem>
+</Tabs>
+
 ## Examples
 
 Copy a file by server-relative URL to a document library in another site collection with server relative URL

package/docs/docs/cmd/file/file-list.mdx

@@ -31,6 +31,25 @@ m365 file list [options]
 
 This command is an improved version of the `spo file list` command. The main difference between the two commands is, that `file list` uses Microsoft Graph and properly supports retrieving files from large folders. Because `file list` uses Microsoft Graph and `spo file list` uses SharePoint REST APIs, the data returned by both commands is different.
 
+## Permissions
+
+<Tabs>
+  <TabItem value="Delegated">
+
+  | Resource        | Permissions                |
+  |-----------------|----------------------------|
+  | Microsoft Graph | Files.Read, Sites.Read.All |
+
+  </TabItem>
+  <TabItem value="Application">
+
+  | Resource        | Permissions                    |
+  |-----------------|--------------------------------|
+  | Microsoft Graph | Files.Read.All, Sites.Read.All |
+
+  </TabItem>
+</Tabs>
+
 ## Examples
 
 Return all files from the folder _Shared Documents_ located in site _https://contoso.sharepoint.com/sites/project-x_

package/docs/docs/cmd/file/file-move.mdx

@@ -1,4 +1,6 @@
 import Global from '../_global.mdx';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
 
 # file move
 
@@ -36,6 +38,25 @@ m365 file move [options]
 - If the source and target locations are within the same document library or drive, the command will utilize the Move DriveItem API, preserving the version history of the file.
 - If the source and target locations are in different document libraries or drives, the command will use a copy-and-delete combination to move the file. Please note that in this case, version history will not be retained.
 
+## Permissions
+
+<Tabs>
+  <TabItem value="Delegated">
+
+  | Resource        | Permissions         |
+  |-----------------|---------------------|
+  | Microsoft Graph | Sites.ReadWrite.All |
+
+  </TabItem>
+  <TabItem value="Application">
+
+  | Resource        | Permissions         |
+  |-----------------|---------------------|
+  | Microsoft Graph | Sites.ReadWrite.All |
+
+  </TabItem>
+</Tabs>
+
 ## Examples
 
 Move a file by server-relative URL to a folder in the same document library

package/docs/docs/cmd/outlook/calendargroup/calendargroup-set.mdx

@@ -0,0 +1,83 @@
+import Global from '../../_global.mdx';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+# outlook calendargroup set
+
+Updates a calendar group for a user.
+
+## Usage
+
+```sh
+m365 outlook calendargroup set [options]
+```
+
+## Options
+
+```md definition-list
+`--id [id]`
+: ID of the calendar group. Specify either `id` or `name`, but not both.
+
+`--name [name]`
+: Name of the calendar group. Specify either `id` or `name`, but not both.
+
+`--userId [userId]`
+: ID of the user. Specify either `userId` or `userName`, but not both.
+
+`--userName [userName]`
+: UPN of the user. Specify either `userId` or `userName`, but not both.
+
+`--newName <newName>`
+: New name of the calendar group.
+```
+
+<Global />
+
+## Permissions
+
+<Tabs>
+  <TabItem value="Delegated">
+
+  | Resource        | Permissions                            |
+  |-----------------|----------------------------------------|
+  | Microsoft Graph | Calendars.ReadWrite, Calendars.ReadWrite.Shared |
+
+  </TabItem>
+  <TabItem value="Application">
+
+  | Resource        | Permissions          |
+  |-----------------|----------------------|
+  | Microsoft Graph | Calendars.ReadWrite  |
+
+  </TabItem>
+</Tabs>
+
+:::note
+
+When using delegated permissions, specifying `userId` or `userName` for a different user requires the `Calendars.ReadWrite.Shared` scope. When the specified user matches the signed-in user, no shared scope is needed.
+
+:::
+
+## Examples
+
+Update the calendar group specified by name for the current user.
+
+```sh
+m365 outlook calendargroup set --name "Personal Evts" --newName "Personal Events"
+```
+
+Update the calendar group specified by id for a user.
+
+```sh
+m365 outlook calendargroup set --id "AAMkADIxYjJiYm" --newName "Personal Events" --userId "44288f7d-7710-4293-8c8e-36f310ed2e6a"
+```
+
+Update the calendar group specified by name for a user specified by email.
+
+```sh
+m365 outlook calendargroup set --name "Personal Evts" --newName "Personal Events" --userName "john.doe@contoso.com"
+```
+
+## Response
+
+The command won't return a response on success.

package/docs/docs/cmd/spfx/project/project-upgrade.mdx

@@ -45,7 +45,7 @@ m365 spfx project upgrade [options]
 
 ## Remarks
 
-The `spfx project upgrade` command helps you upgrade your SharePoint Framework project to the specified version. If no version is specified, the command will upgrade to the latest version of the SharePoint Framework it supports (v1.22.2).
+The `spfx project upgrade` command helps you upgrade your SharePoint Framework project to the specified version. If no version is specified, the command will upgrade to the latest version of the SharePoint Framework it supports (v1.23.0-rc.0).
 
 This command doesn't change your project files. Instead, it gives you a report with all steps necessary to upgrade your project to the specified version of the SharePoint Framework. Changing project files is error-prone, especially when it comes to updating your solution's code. This is why at this moment, this command produces a report that you can use yourself to perform the necessary updates and verify that everything is working as expected.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnp/cli-microsoft365",
-  "version": "11.7.0-beta.b9f508d",
+  "version": "11.7.0-beta.bd906c5",
   "description": "Manage Microsoft 365 and SharePoint Framework projects on any platform",
   "license": "MIT",
   "main": "./dist/api.js",