@pnp/cli-microsoft365 5.0.0-beta.fa7a63b → 5.0.0-beta.fe151d6

package/dist/m365/spo/commands/site/site-remove.js

@@ -25,26 +25,65 @@ class SpoSiteRemoveCommand extends SpoCommand_1.default {
     commandAction(logger, args, cb) {
         const removeSite = () => {
             this.dots = '';
-            this
-                .getSiteGroupId(args.options.url, logger)
-                .then((_groupId) => {
-                if (_groupId === '00000000-0000-0000-0000-000000000000') {
-                    if (this.debug) {
-                        logger.logToStderr('Site is not groupified. Going ahead with the conventional site deletion options');
-                    }
-                    return this.deleteSiteWithoutGroup(logger, args);
-                }
-                else {
-                    if (this.debug) {
-                        logger.logToStderr(`Site attached to group ${_groupId}. Initiating group delete operation via Graph API`);
+            if (args.options.fromRecycleBin) {
+                this
+                    .deleteSiteWithoutGroup(logger, args)
+                    .then(_ => cb(), (err) => this.handleRejectedPromise(err, logger, cb));
+            }
+            else {
+                this
+                    .getSiteGroupId(args.options.url, logger)
+                    .then((groupId) => {
+                    if (groupId === '00000000-0000-0000-0000-000000000000') {
+                        if (this.debug) {
+                            logger.logToStderr('Site is not groupified. Going ahead with the conventional site deletion options');
+                        }
+                        return this.deleteSiteWithoutGroup(logger, args);
                     }
-                    if (args.options.fromRecycleBin || args.options.skipRecycleBin || args.options.wait) {
-                        logger.log(chalk.yellow(`Entered site is a groupified site. Hence, the parameters 'fromRecycleBin' or 'skipRecycleBin' or 'wait' will not be applicable.`));
+                    else {
+                        if (this.debug) {
+                            logger.logToStderr(`Site attached to group ${groupId}. Initiating group delete operation via Graph API`);
+                        }
+                        return this
+                            .getSiteGroup(groupId)
+                            .then((group) => {
+                            if (args.options.skipRecycleBin || args.options.wait) {
+                                logger.logToStderr(chalk.yellow(`Entered site is a groupified site. Hence, the parameters 'skipRecycleBin' and 'wait' will not be applicable.`));
+                            }
+                            return this.deleteGroupifiedSite(group.id, logger);
+                        })
+                            .catch((err) => {
+                            if (err.response.status === 404) {
+                                if (this.verbose) {
+                                    logger.logToStderr(`Site group doesn't exist. Searching in the Microsoft 365 deleted groups.`);
+                                }
+                                return this
+                                    .isSiteGroupDeleted(groupId)
+                                    .then((deletedGroups) => {
+                                    if (deletedGroups.value.length === 0) {
+                                        if (this.verbose) {
+                                            logger.logToStderr("Site group doesn't exist anymore. Deleting the site.");
+                                        }
+                                        if (args.options.wait) {
+                                            logger.logToStderr(chalk.yellow(`Entered site is a groupified site. Hence, the parameter 'wait' will not be applicable.`));
+                                        }
+                                        return Promise.resolve();
+                                    }
+                                    else {
+                                        return Promise.reject(`Site group still exists in the deleted groups. The site won't be removed.`);
+                                    }
+                                })
+                                    .then(_ => this.deleteOrphanedSite(logger, args.options.url))
+                                    .catch((err) => Promise.reject(err));
+                            }
+                            else {
+                                return Promise.reject(err);
+                            }
+                        });
                     }
-                    return this.deleteGroupifiedSite(_groupId, logger);
-                }
-            })
-                .then(_ => cb(), (err) => this.handleRejectedPromise(err, logger, cb));
+                })
+                    .then(_ => cb(), (err) => this.handleRejectedPromise(err, logger, cb));
+            }
         };
         if (args.options.confirm) {
             removeSite();
@@ -65,32 +104,64 @@ class SpoSiteRemoveCommand extends SpoCommand_1.default {
             });
         }
     }
+    getSiteGroup(groupId) {
+        const requestOptions = {
+            url: `https://graph.microsoft.com/v1.0/groups/${groupId}`,
+            headers: {
+                accept: 'application/json;odata.metadata=none'
+            },
+            responseType: 'json'
+        };
+        return request_1.default.get(requestOptions);
+    }
+    isSiteGroupDeleted(groupId) {
+        const requestOptions = {
+            url: `https://graph.microsoft.com/v1.0/directory/deletedItems/Microsoft.Graph.Group?$select=id&$filter=groupTypes/any(c:c+eq+'Unified') and startswith(id, '${groupId}')`,
+            headers: {
+                accept: 'application/json;odata.metadata=none'
+            },
+            responseType: 'json'
+        };
+        return request_1.default.get(requestOptions);
+    }
+    deleteOrphanedSite(logger, url) {
+        return this
+            .getSpoAdminUrl(logger, this.debug)
+            .then((spoAdminUrl) => {
+            const requestOptions = {
+                url: `${spoAdminUrl}/_api/GroupSiteManager/Delete?siteUrl='${url}'`,
+                headers: {
+                    'content-type': 'application/json;odata=nometadata',
+                    accept: 'application/json;odata=nometadata'
+                },
+                responseType: 'json'
+            };
+            return request_1.default.post(requestOptions);
+        });
+    }
     deleteSiteWithoutGroup(logger, args) {
         return this
             .getSpoAdminUrl(logger, this.debug)
-            .then((_spoAdminUrl) => {
-            this.spoAdminUrl = _spoAdminUrl;
+            .then((spoAdminUrl) => {
+            this.spoAdminUrl = spoAdminUrl;
             return this.ensureFormDigest(this.spoAdminUrl, logger, this.context, this.debug);
         })
             .then((res) => {
             this.context = res;
             if (args.options.fromRecycleBin) {
                 if (this.verbose) {
-                    logger.logToStderr(`Deleting site collection from recycle bin ${args.options.url}...`);
+                    logger.logToStderr(`Deleting site from recycle bin ${args.options.url}...`);
                 }
                 return this.deleteSiteFromTheRecycleBin(args.options.url, args.options.wait, logger);
             }
             else {
-                if (this.verbose) {
-                    logger.logToStderr(`Deleting site collection ${args.options.url}...`);
-                }
                 return this.deleteSite(args.options.url, args.options.wait, logger);
             }
         })
             .then(() => {
             if (args.options.skipRecycleBin) {
                 if (this.verbose) {
-                    logger.logToStderr(`Also deleting site collection from recycle bin ${args.options.url}...`);
+                    logger.logToStderr(`Also deleting site from tenant recycle bin ${args.options.url}...`);
                 }
                 return this.deleteSiteFromTheRecycleBin(args.options.url, args.options.wait, logger);
             }
@@ -106,7 +177,7 @@ class SpoSiteRemoveCommand extends SpoCommand_1.default {
                 .then((res) => {
                 this.context = res;
                 if (this.verbose) {
-                    logger.logToStderr(`Deleting site ${url} ...`);
+                    logger.logToStderr(`Deleting site ${url}...`);
                 }
                 const requestOptions = {
                     url: `${this.spoAdminUrl}/_vti_bin/client.svc/ProcessQuery`,
@@ -143,9 +214,6 @@ class SpoSiteRemoveCommand extends SpoCommand_1.default {
                 .ensureFormDigest(this.spoAdminUrl, logger, this.context, this.debug)
                 .then((res) => {
                 this.context = res;
-                if (this.verbose) {
-                    logger.logToStderr(`Deleting site ${url} from the recycle bin...`);
-                }
                 const requestOptions = {
                     url: `${this.spoAdminUrl}/_vti_bin/client.svc/ProcessQuery`,
                     headers: {
@@ -185,7 +253,7 @@ class SpoSiteRemoveCommand extends SpoCommand_1.default {
             .then((res) => {
             this.context = res;
             if (this.verbose) {
-                logger.logToStderr(`Retrieving the GroupId of the site  ${url}`);
+                logger.logToStderr(`Retrieving the group Id of the site ${url}`);
             }
             const requestOptions = {
                 url: `${this.spoAdminUrl}/_vti_bin/client.svc/ProcessQuery`,

package/dist/m365/spo/commands.js

@@ -22,9 +22,10 @@ exports.default = {
     CDN_POLICY_SET: `${prefix} cdn policy set`,
     CDN_SET: `${prefix} cdn set`,
     CONTENTTYPE_ADD: `${prefix} contenttype add`,
-    CONTENTTYPE_GET: `${prefix} contenttype get`,
     CONTENTTYPE_FIELD_REMOVE: `${prefix} contenttype field remove`,
     CONTENTTYPE_FIELD_SET: `${prefix} contenttype field set`,
+    CONTENTTYPE_GET: `${prefix} contenttype get`,
+    CONTENTTYPE_LIST: `${prefix} contenttype list`,
     CONTENTTYPE_REMOVE: `${prefix} contenttype remove`,
     CONTENTTYPEHUB_GET: `${prefix} contenttypehub get`,
     CUSTOMACTION_ADD: `${prefix} customaction add`,

package/dist/m365/teams/commands/report/report-directroutingcalls.js

@@ -22,7 +22,7 @@ class TeamsReportDirectroutingcallsCommand extends GraphCommand_1.default {
     commandAction(logger, args, cb) {
         const toDateTimeParameter = encodeURIComponent(args.options.toDateTime ? args.options.toDateTime : new Date().toISOString());
         const requestOptions = {
-            url: `${this.resource}/beta/communications/callRecords/getDirectRoutingCalls(fromDateTime=${encodeURIComponent(args.options.fromDateTime)},toDateTime=${toDateTimeParameter})`,
+            url: `${this.resource}/v1.0/communications/callRecords/getDirectRoutingCalls(fromDateTime=${encodeURIComponent(args.options.fromDateTime)},toDateTime=${toDateTimeParameter})`,
             headers: {
                 accept: 'application/json;odata.metadata=none'
             },

package/docs/docs/cmd/aad/app/app-add.md

@@ -52,6 +52,9 @@ m365 aad app add [options]
 `--manifest [manifest]`
 : Azure AD app manifest as retrieved from the Azure Portal to create the app registration from
 
+`--save`
+: Use to store the information about the created app in a local file
+
 --8<-- "docs/cmd/_global.md"
 
 ## Remarks
@@ -80,6 +83,8 @@ When using the `withSecret` option, this command will automatically generate a s
 
 After creating the Azure AD app registration, this command returns the app ID and object ID of the created app registration. If you used the `withSecret` option, it will also return the generated secret.
 
+If you want to store the information about the created Azure AD app registration, use the `--save` option. This is useful when you build solutions connected to Microsoft 365 and want to easily manage app registrations used with your solution. When you use the `--save` option, after you create the app registration, the command will write its ID and name to the `.m365rc.json` file in the current directory. If the file already exists, it will add the information about the to it, allowing you to track multiple apps. If the file doesn't exist, the command will create it.
+
 ## Examples
 
 Create new Azure AD app registration with the specified name
@@ -141,3 +146,9 @@ Create new Azure AD app registration with Application ID URI set to a value that
 ```sh
 m365 aad app add --name 'My AAD app' --uri api://caf406b91cd4.ngrok.io/_appId_ --scopeName access_as_user --scopeAdminConsentDescription 'Access as a user' --scopeAdminConsentDisplayName 'Access as a user' --scopeConsentBy adminsAndUsers
 ```
+
+Create new Azure AD app registration with the specified name. Store information about the created app registration in the _.m365rc.json_ file in the current directory.
+
+```sh
+m365 aad app add --name 'My AAD app' --save
+```

package/docs/docs/cmd/aad/o365group/o365group-add.md

@@ -36,6 +36,7 @@ m365 aad o365group add [options]
 ## Remarks
 
 When specifying the path to the logo image you can use both relative and absolute paths. Note, that ~ in the path, will not be resolved and will most likely result in an error.
+If an invalid user is provided in the comma-separated list or Owners or Members, the command operation will fail and the Micrsoft 365 Group will not be created.
 
 ## Examples
 

package/docs/docs/cmd/aad/oauth2grant/oauth2grant-list.md

@@ -10,7 +10,7 @@ m365 aad oauth2grant list [options]
 
 ## Options
 
-`-i, --clientId <clientId>`
+`-i, --spObjectId <spObjectId>`
 : objectId of the service principal for which the configured OAuth2 permission grants should be retrieved
 
 --8<-- "docs/cmd/_global.md"
@@ -26,7 +26,7 @@ When using the text output type (default), the command lists only the values of
 List OAuth2 permissions granted to service principal with `objectId` _b2307a39-e878-458b-bc90-03bc578531d6_.
 
 ```sh
-m365 aad oauth2grant list --clientId b2307a39-e878-458b-bc90-03bc578531d6
+m365 aad oauth2grant list --spObjectId b2307a39-e878-458b-bc90-03bc578531d6
 ```
 
 ## More information

package/docs/docs/cmd/aad/oauth2grant/oauth2grant-remove.md

@@ -13,6 +13,9 @@ m365 aad oauth2grant remove [options]
 `-i, --grantId <grantId>`
 : `objectId` of OAuth2 permission grant to remove
 
+`--confirm`
+: Do not prompt for confirmation before removing OAuth2 permission grant
+
 --8<-- "docs/cmd/_global.md"
 
 ## Remarks
@@ -33,6 +36,12 @@ Remove the OAuth2 permission grant with ID _YgA60KYa4UOPSdc-lpxYEnQkr8KVLDpCsOXk
 m365 aad oauth2grant remove --grantId YgA60KYa4UOPSdc-lpxYEnQkr8KVLDpCsOXkiV8i-ek
 ```
 
+Remove the OAuth2 permission grant with ID _YgA60KYa4UOPSdc-lpxYEnQkr8KVLDpCsOXkiV8i-ek_ without being asked for confirmation
+
+```sh
+m365 aad oauth2grant remove --grantId YgA60KYa4UOPSdc-lpxYEnQkr8KVLDpCsOXkiV8i-ek --confirm
+```
+
 ## More information
 
 - Application and service principal objects in Azure Active Directory (Azure AD): [https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-application-objects](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-application-objects)

package/docs/docs/cmd/aad/sp/sp-add.md

@@ -0,0 +1,53 @@
+# aad sp add
+
+Adds a service principal to a registered Azure AD app
+
+## Usage
+
+```sh
+m365 aad sp add [options]
+```
+
+## Options
+
+`--appId [appId]`
+: ID of the application to which the service principal should be added
+
+`--appName [appName]`
+: Display name of the application to which the service principal should be added
+
+`--objectId [objectId]`
+: ObjectId of the application to which the service principal should be added
+
+--8<-- "docs/cmd/_global.md"
+
+## Remarks
+
+Specify either the `appId`, `appName` or `objectId`. If you specify more than one option value, the command will fail with an error.
+
+If you register an application in the portal, an application object as well as a service principal object are automatically created in your home tenant. If you register an application using CLI for Microsoft 365 or the Microsoft Graph, you'll need to create the service principal separately. To register/create an application using the CLI for Microsoft 365, use the [m365 aad app add](../app/app-add.md) command.
+
+## Examples
+
+Adds a service principal to a registered Azure AD app with appId _b2307a39-e878-458b-bc90-03bc578531d6_.
+
+```sh
+m365 aad sp add --appId b2307a39-e878-458b-bc90-03bc578531d6
+```
+
+Adds a service principal to a registered Azure AD app with appName _Microsoft Graph_.
+
+```sh
+m365 aad sp add --appName "Microsoft Graph"
+```
+
+Adds a service principal to a registered Azure AD app with objectId _b2307a39-e878-458b-bc90-03bc578531d6_.
+
+```sh
+m365 aad sp add --objectId b2307a39-e878-458b-bc90-03bc578531d6
+```
+
+## More information
+
+- Application and service principal objects in Azure Active Directory (Azure AD): [https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-application-objects](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-application-objects)
+- Create servicePrincipal: [https://docs.microsoft.com/en-us/graph/api/serviceprincipal-post-serviceprincipals?view=graph-rest-1.0](https://docs.microsoft.com/en-us/graph/api/serviceprincipal-post-serviceprincipals?view=graph-rest-1.0)

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

@@ -16,12 +16,17 @@ m365 file add [options]
 `-p, --filePath <filePath>`
 : Local path to the file to upload
 
+`--siteUrl [siteUrl]`
+: URL of the site to which upload the file. Specify to suppress lookup.
+
 --8<-- "docs/cmd/_global.md"
 
 ## Remarks
 
 The `folderUrl` must be an absolute URL to the document library where the file should be uploaded. The document library can be located in any site collection in your tenant, including OneDrive for Business. The `folderUrl` can also point to a (sub)folder in the document library.
 
+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 Azure AD app only has access to the specific site, you can use the `siteUrl` option to specify the URL of the site yourself.
+
 ## Examples
 
 Uploads file from the current folder to the root folder of a document library in the root site collection
@@ -47,3 +52,9 @@ Uploads file from the current folder to a document library in a non-root site co
 ```sh
 m365 file add --filePath file.pdf --folderUrl "https://contoso.sharepoint.com/sites/Contoso/Shared Documents"
 ```
+
+Uploads file from the current folder to a document library in the specified site
+
+```sh
+m365 file add --filePath file.pdf --folderUrl "https://contoso.sharepoint.com/sites/Contoso/Shared Documents" --siteUrl "https://contoso.sharepoint.com/sites/Contoso"
+```

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

@@ -0,0 +1,46 @@
+# file list
+
+Retrieves files from the specified folder and site
+
+## Usage
+
+```sh
+m365 file list [options]
+```
+
+## Options
+
+`-u, --webUrl <webUrl>`
+: The URL of the site where the folder from which to retrieve files is located
+
+`-f, --folderUrl <folderUrl>`
+: The server- or site-relative URL of the folder from which to retrieve files
+
+`--recursive`
+: Set to retrieve files from subfolders
+
+--8<-- "docs/cmd/_global.md"
+
+## Remarks
+
+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.
+
+## Examples
+
+Return all files from folder _Shared Documents_ located in site _https://contoso.sharepoint.com/sites/project-x_
+
+```sh
+m365 file list --webUrl https://contoso.sharepoint.com/sites/project-x --folder 'Shared Documents'
+```
+
+Return all files from the folder _Shared Documents_ and all the sub-folders of _Shared Documents_ located in site _https://contoso.sharepoint.com/sites/project-x_
+
+```sh
+m365 file list --webUrl https://contoso.sharepoint.com/sites/project-x --folder 'Shared Documents' --recursive
+```
+
+Return all files from the _Important_ folder in the _Shared Documents_ document library located in site _https://contoso.sharepoint.com/sites/project-x_
+
+```sh
+m365 file list --webUrl https://contoso.sharepoint.com/sites/project-x --folder 'Shared Documents/Important'
+```

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

@@ -32,7 +32,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.13.0).
+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.13.1).
 
 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/docs/docs/cmd/spo/contenttype/contenttype-list.md

@@ -0,0 +1,33 @@
+# spo contenttype list
+
+Lists content types from specified site
+
+## Usage
+
+```sh
+m365 spo contenttype list [options]
+```
+
+## Options
+
+`-u, --webUrl <webUrl>`
+: Absolute URL of the site for which to list content types
+
+`-c, --category [category]`
+: Category name of content types. When defined will return only content types from specified category
+
+--8<-- "docs/cmd/_global.md"
+
+## Examples
+
+Retrieve site content types
+
+```PowerShell
+m365 spo contenttype list --webUrl "https://contoso.sharepoint.com/sites/contoso-sales"
+```
+
+Retrieve site content types from the 'List Content Types' category
+
+```PowerShell
+m365 spo contenttype list --webUrl "https://contoso.sharepoint.com/sites/contoso-sales" --category "List Content Types"
+```

package/docs/docs/cmd/spo/list/list-get.md

@@ -22,6 +22,9 @@ m365 spo list get [options]
 `-p, --properties [properties]`
 : Comma-separated list of properties to retrieve from the list. Will retrieve all properties possible from default response, if not specified.
 
+`--withPermissions`
+: Set if you want to return associated roles and permissions of the list.
+
 --8<-- "docs/cmd/_global.md"
 
 ## Examples
@@ -44,6 +47,12 @@ Get information about a list returning the specified list properties
 m365 spo list get --title Documents --webUrl https://contoso.sharepoint.com/sites/project-x --properties "Title,Id,HasUniqueRoleAssignments,AllowContentTypes"
 ```
 
+Get information about a list along with the roles and permissions
+
+```sh
+m365 spo list get --title Documents --webUrl https://contoso.sharepoint.com/sites/project-x --withPermissions
+```
+
 ## More information
 
 - List REST API resources: [https://msdn.microsoft.com/en-us/library/office/dn531433.aspx#bk_ListEndpoint](https://msdn.microsoft.com/en-us/library/office/dn531433.aspx#bk_ListEndpoint)

package/docs/docs/cmd/spo/page/page-add.md

@@ -20,10 +20,10 @@ m365 spo page add [options]
 : Title of the page to create. If not specified, will use the page name as its title
 
 `-l, --layoutType [layoutType]`
-: Layout of the page. Allowed values `Article,Home`. Default `Article`
+: Layout of the page. Allowed values `Article`, `Home`, `SingleWebPartAppPage`, `RepostPage`,`HeaderlessSearchResults`, `Spaces`, `Topic`. Default `Article`
 
 `-p, --promoteAs [promoteAs]`
-: Create the page for a specific purpose. Allowed values `HomePage,NewsPage`
+: Create the page for a specific purpose. Allowed values `HomePage`, `NewsPage`
 
 `--commentsEnabled`
 : Set to enable comments on the page

package/docs/docs/cmd/spo/page/page-set.md

@@ -17,13 +17,13 @@ m365 spo page set [options]
 : URL of the site where the page to update is located
 
 `-l, --layoutType [layoutType]`
-: Layout of the page. Allowed values `Article,Home`
+: Layout of the page. Allowed values `Article`, `Home`, `SingleWebPartAppPage`, `RepostPage`,`HeaderlessSearchResults`, `Spaces`, `Topic`
 
 `-p, --promoteAs [promoteAs]`
-: Update the page purpose. Allowed values `HomePage,NewsPage`
+: Update the page purpose. Allowed values `HomePage`, `NewsPage`
 
 `--commentsEnabled [commentsEnabled]`
-: Set to `true`, to enable comments on the page. Allowed values `true,false`
+: Set to `true`, to enable comments on the page. Allowed values `true`, `false`
 
 `--publish`
 : Set to publish the page

package/docs/docs/cmd/spo/site/site-remove.md

@@ -34,7 +34,9 @@ m365 spo site remove [options]
 
 Deleting a site collection is by default asynchronous and depending on the current state of Microsoft 365, might take up to few minutes. If you're building a script with steps that require the site to be fully deleted, you should use the `--wait` flag. When using this flag, the `spo site remove` command will keep running until it received confirmation from Microsoft 365 that the site has been fully deleted.
 
-If the site which you have selected to remove is groupified (Modern Team Site), flags `--fromRecycleBin`, `--skipRecycleBin` and `--wait` will not be applicable
+If the site which you have selected to remove is groupified (Modern Team Site) and group exists, flags `--skipRecycleBin` and `--wait` will not be applicable. If the linked group still exists in the deleted groups, the site won't be removed. If the linked group is permanently deleted, the site will be removed like any classic site (except that flag `--wait` only will still not be applicable).
+
+If the argument `--fromRecycleBin` is passed, the selected site will be permanently removed even if it's a groupified one.
 
 ## Examples
 

package/docs/docs/cmd/teams/report/report-directroutingcalls.md

@@ -24,9 +24,6 @@ This command only works with app-only permissions. You will need to create your
 
 The difference between `fromDateTime` and `toDateTime` cannot exceed a period of 90 days
 
-!!! attention
-    This command is based on an API that is currently in preview and is subject to change once the API reached general availability.
-
 ## Examples
 
 Get details about direct routing calls made between 2020-10-31 and today