@pnp/cli-microsoft365 7.5.0-beta.23612bc → 7.5.0-beta.4f8e5bf

package/dist/m365/viva/commands.js

@@ -1,5 +1,26 @@
 const prefix = 'viva';
 export default {
-    CONNECTIONS_APP_CREATE: `${prefix} connections app create`
+    CONNECTIONS_APP_CREATE: `${prefix} connections app create`,
+    ENGAGE_GROUP_LIST: `${prefix} engage group list`,
+    ENGAGE_GROUP_USER_ADD: `${prefix} engage group user add`,
+    ENGAGE_GROUP_USER_REMOVE: `${prefix} engage group user remove`,
+    ENGAGE_MESSAGE_ADD: `${prefix} engage message add`,
+    ENGAGE_MESSAGE_GET: `${prefix} engage message get`,
+    ENGAGE_MESSAGE_LIKE_SET: `${prefix} engage message like set`,
+    ENGAGE_MESSAGE_LIST: `${prefix} engage message list`,
+    ENGAGE_MESSAGE_REMOVE: `${prefix} engage message remove`,
+    ENGAGE_NETWORK_LIST: `${prefix} engage network list`,
+    ENGAGE_REPORT_ACTIVITYCOUNTS: `${prefix} engage report activitycounts`,
+    ENGAGE_REPORT_ACTIVITYUSERCOUNTS: `${prefix} engage report activityusercounts`,
+    ENGAGE_REPORT_ACTIVITYUSERDETAIL: `${prefix} engage report activityuserdetail`,
+    ENGAGE_REPORT_DEVICEUSAGEDISTRIBUTIONUSERCOUNTS: `${prefix} engage report deviceusagedistributionusercounts`,
+    ENGAGE_REPORT_DEVICEUSAGEUSERCOUNTS: `${prefix} engage report deviceusageusercounts`,
+    ENGAGE_REPORT_DEVICEUSAGEUSERDETAIL: `${prefix} engage report deviceusageuserdetail`,
+    ENGAGE_REPORT_GROUPSACTIVITYCOUNTS: `${prefix} engage report groupsactivitycounts`,
+    ENGAGE_REPORT_GROUPSACTIVITYDETAIL: `${prefix} engage report groupsactivitydetail`,
+    ENGAGE_REPORT_GROUPSACTIVITYGROUPCOUNTS: `${prefix} engage report groupsactivitygroupcounts`,
+    ENGAGE_SEARCH: `${prefix} engage search`,
+    ENGAGE_USER_GET: `${prefix} engage user get`,
+    ENGAGE_USER_LIST: `${prefix} engage user list`
 };
 //# sourceMappingURL=commands.js.map

package/dist/request.js

@@ -130,7 +130,7 @@ class Request {
         if (!this._logger) {
             return Promise.reject('Logger not set on the request object');
         }
-        this.updateRequestForCloudType(options, auth.service.cloudType);
+        this.updateRequestForCloudType(options, auth.connection.cloudType);
         return new Promise((_resolve, _reject) => {
             (() => {
                 if (options.headers && options.headers['x-anonymous']) {

package/dist/utils/spo.js

@@ -96,11 +96,11 @@ export const spo = {
         });
     },
     async getSpoUrl(logger, debug) {
-        if (auth.service.spoUrl) {
+        if (auth.connection.spoUrl) {
             if (debug) {
-                await logger.logToStderr(`SPO URL previously retrieved ${auth.service.spoUrl}. Returning...`);
+                await logger.logToStderr(`SPO URL previously retrieved ${auth.connection.spoUrl}. Returning...`);
             }
-            return Promise.resolve(auth.service.spoUrl);
+            return Promise.resolve(auth.connection.spoUrl);
         }
         return new Promise(async (resolve, reject) => {
             if (debug) {
@@ -116,14 +116,14 @@ export const spo = {
             request
                 .get(requestOptions)
                 .then((res) => {
-                auth.service.spoUrl = res.webUrl;
+                auth.connection.spoUrl = res.webUrl;
                 return auth.storeConnectionInfo();
             })
                 .then(() => {
-                resolve(auth.service.spoUrl);
+                resolve(auth.connection.spoUrl);
             }, (err) => {
-                if (auth.service.spoUrl) {
-                    resolve(auth.service.spoUrl);
+                if (auth.connection.spoUrl) {
+                    resolve(auth.connection.spoUrl);
                 }
                 else {
                     reject(err);
@@ -143,11 +143,11 @@ export const spo = {
         });
     },
     async getTenantId(logger, debug) {
-        if (auth.service.tenantId) {
+        if (auth.connection.spoTenantId) {
             if (debug) {
-                await logger.logToStderr(`SPO Tenant ID previously retrieved ${auth.service.tenantId}. Returning...`);
+                await logger.logToStderr(`SPO Tenant ID previously retrieved ${auth.connection.spoTenantId}. Returning...`);
             }
-            return Promise.resolve(auth.service.tenantId);
+            return Promise.resolve(auth.connection.spoTenantId);
         }
         return new Promise(async (resolve, reject) => {
             if (debug) {
@@ -173,14 +173,14 @@ export const spo = {
             })
                 .then((res) => {
                 const json = JSON.parse(res);
-                auth.service.tenantId = json[json.length - 1]._ObjectIdentity_.replace('\n', '
');
+                auth.connection.spoTenantId = json[json.length - 1]._ObjectIdentity_.replace('\n', '
');
                 return auth.storeConnectionInfo();
             })
                 .then(() => {
-                resolve(auth.service.tenantId);
+                resolve(auth.connection.spoTenantId);
             }, (err) => {
-                if (auth.service.tenantId) {
-                    resolve(auth.service.tenantId);
+                if (auth.connection.spoTenantId) {
+                    resolve(auth.connection.spoTenantId);
                 }
                 else {
                     reject(err);
@@ -1312,6 +1312,28 @@ export const spo = {
             responseType: 'json'
         };
         await request.post(requestOptions);
+    },
+    /**
+     * Retrieves the site ID for a given web URL.
+     * @param webUrl The web URL for which to retrieve the site ID.
+     * @param logger The logger object.
+     * @param verbose Set for verbose logging
+     * @returns A promise that resolves to the site ID.
+     */
+    async getSiteId(webUrl, logger, verbose) {
+        if (verbose && logger) {
+            logger.logToStderr(`Getting site id for URL: ${webUrl}...`);
+        }
+        const url = new URL(webUrl);
+        const requestOptions = {
+            url: `https://graph.microsoft.com/v1.0/sites/${formatting.encodeQueryParameter(url.host)}:${url.pathname}?$select=id`,
+            headers: {
+                accept: 'application/json;odata.metadata=none'
+            },
+            responseType: 'json'
+        };
+        const site = await request.get(requestOptions);
+        return site.id;
     }
 };
 //# sourceMappingURL=spo.js.map

package/dist/utils/urlUtil.js

@@ -166,6 +166,37 @@ export const urlUtil = {
             relativeUrl = relativeUrl.substring(0, relativeUrl.length - 1);
         }
         return `${baseUrl}/${relativeUrl}`;
+    },
+    /**
+     * Get the absolute URL from the target SharePoint URL.
+     * @param {string} webUrl - The base web URL.
+     * @param {string} url - The target SharePoint URL.
+     * @returns {string} - The target site absolute URL.
+     *
+     * Example Scenarios:
+     * - webUrl = "https://contoso.sharepoint.com" and targetUrl = "/teams/sales/Shared Documents/temp/123/234",
+     *    returns "https://contoso.sharepoint.com/teams/sales".
+     * - webUrl = "https://contoso.sharepoint.com" and targetUrl = "https://contoso-my.sharepoint.com/personal/john_contoso_onmicrosoft_com/Documents/123",
+     *    returns "https://contoso-my.sharepoint.com/personal/john_contoso_onmicrosoft_com".
+     * - webUrl = "https://contoso.sharepoint.com/teams/sales" and targetUrl = "/Shared Documents/temp",
+     *    returns "https://contoso.sharepoint.com".
+     * - webUrl = "https://contoso.sharepoint.com" and targetUrl = "/teams/sales/Shared Documents/temp",
+     *    returns "https://contoso.sharepoint.com/teams/sales".
+    */
+    getTargetSiteAbsoluteUrl(webUrl, url) {
+        const fullUrl = url.startsWith('https://') ? url : urlUtil.getAbsoluteUrl(webUrl, url);
+        // Pattern to match SharePoint URLs
+        const urlPattern = /https:\/\/[\w\-]+\.sharepoint\.com\/(teams|sites|personal)\/([\w\-]+)/;
+        const match = fullUrl.match(urlPattern);
+        if (match) {
+            // If a match is found, return the matched URL
+            return match[0];
+        }
+        else {
+            // Extract the root URL
+            const rootUrl = new URL(fullUrl);
+            return rootUrl.origin;
+        }
     }
 };
 //# sourceMappingURL=urlUtil.js.map

package/dist/utils/validation.js

@@ -321,6 +321,10 @@ export const validation = {
             return true;
         }
         return false;
+    },
+    isValidMailNickname(mailNickname) {
+        const mailNicknameRegEx = new RegExp(/^[a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-]*$/i);
+        return mailNicknameRegEx.test(mailNickname);
     }
 };
 //# sourceMappingURL=validation.js.map

package/docs/docs/cmd/cli/cli-consent.mdx

@@ -16,25 +16,25 @@ m365 cli consent [options]
 
 ```md definition-list
 `-s, --service <service>`
-: Service for which to consent permissions. Allowed values: `yammer`
+: Service for which to consent permissions. Allowed values: `VivaEngage`, (deprecated)`yammer`.
 ```
 
 <Global />
 
 ## Remarks
 
-Using the `cli consent` command you can consent additional permissions for the Azure AD application used by the CLI for Microsoft 365. This is for example necessary to use Yammer commands, which require the Yammer API permission that isn't granted to the CLI by default.
+Using the `cli consent` command you can consent additional permissions for the Azure AD application used by the CLI for Microsoft 365. This is for example necessary to use Viva Engage commands, which require the Viva Engage API permission that isn't granted to the CLI by default.
 
 After executing the command, the CLI for Microsoft 365 will present you with a URL that you need to open in the web browser in order to consent the permissions for the selected Microsoft 365 service.
 
-To simplify things, rather than wondering which permissions you should grant for which CLI commands, this command allows you to easily grant all the necessary permissions for using commands for the specified Microsoft 365 service, like Yammer.
+To simplify things, rather than wondering which permissions you should grant for which CLI commands, this command allows you to easily grant all the necessary permissions for using commands for the specified Microsoft 365 service, like Viva Engage.
 
 ## Examples
 
-Consent permissions to the Yammer API
+Consent permissions to the Viva Engage API
 
 ```sh
-m365 cli consent --service yammer
+m365 cli consent --service VivaEngage
 ```
 
 ## Response
@@ -43,28 +43,28 @@ m365 cli consent --service yammer
   <TabItem value="JSON">
 
   ```json
-  "To consent permissions for executing yammer commands, navigate in your web browser to https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=31359c7f-bd7e-475c-86db-fdb8c937548e&response_type=code&scope=https%3A%2F%2Fapi.yammer.com%2Fuser_impersonation"
+  "To consent permissions for executing VivaEngage commands, navigate in your web browser to https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=31359c7f-bd7e-475c-86db-fdb8c937548e&response_type=code&scope=https%3A%2F%2Fapi.yammer.com%2Fuser_impersonation"
   ```
 
   </TabItem>
   <TabItem value="Text">
 
   ```text
-  To consent permissions for executing yammer commands, navigate in your web browser to https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=31359c7f-bd7e-475c-86db-fdb8c937548e&response_type=code&scope=https%3A%2F%2Fapi.yammer.com%2Fuser_impersonation
+  To consent permissions for executing VivaEngage commands, navigate in your web browser to https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=31359c7f-bd7e-475c-86db-fdb8c937548e&response_type=code&scope=https%3A%2F%2Fapi.yammer.com%2Fuser_impersonation
   ```
 
   </TabItem>
   <TabItem value="CSV">
 
   ```csv
-  To consent permissions for executing yammer commands, navigate in your web browser to https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=31359c7f-bd7e-475c-86db-fdb8c937548e&response_type=code&scope=https%3A%2F%2Fapi.yammer.com%2Fuser_impersonation
+  To consent permissions for executing VivaEngage commands, navigate in your web browser to https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=31359c7f-bd7e-475c-86db-fdb8c937548e&response_type=code&scope=https%3A%2F%2Fapi.yammer.com%2Fuser_impersonation
   ```
 
   </TabItem>
   <TabItem value="Markdown">
 
   ```md
-  To consent permissions for executing yammer commands, navigate in your web browser to https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=31359c7f-bd7e-475c-86db-fdb8c937548e&response_type=code&scope=https%3A%2F%2Fapi.yammer.com%2Fuser_impersonation
+  To consent permissions for executing VivaEngage commands, navigate in your web browser to https://login.microsoftonline.com/common/oauth2/v2.0/authorize?client_id=31359c7f-bd7e-475c-86db-fdb8c937548e&response_type=code&scope=https%3A%2F%2Fapi.yammer.com%2Fuser_impersonation
   ```
 
   </TabItem>

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

@@ -0,0 +1,100 @@
+import Global from '/docs/cmd/_global.mdx';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+# connection list
+
+Show the list of available connections
+
+## Usage
+
+```sh
+m365 connection list [options]
+```
+
+## Options
+
+<Global />
+
+## Remarks
+
+If you are logged in to Microsoft 365 with multiple identities, this command will show you a list of users and/or applications used to sign in.  
+
+## Examples
+
+Show the list of available identities used to sign in to Microsoft 365
+
+```sh
+m365 connection list
+```
+
+## Response
+
+<Tabs>
+  <TabItem value="JSON">
+
+  ```json
+  [
+    {
+      "name": "028de82d-7fd9-476e-a9fd-be9714280ff3",
+      "connectedAs": "alexw@contoso.com",
+      "authType": "DeviceCode",
+      "active": true
+    },
+    {
+      "name": "acd6df42-10a9-4315-8928-53334f1c9d01",
+      "connectedAs": "Contoso Application",
+      "authType": "Secret",
+      "active": false
+    }
+  ]
+  ```
+
+  </TabItem>
+  <TabItem value="Text">
+
+  ```text
+  name                                  connectedAs          authType    active
+  ------------------------------------  -------------------  ----------  ------
+  028de82d-7fd9-476e-a9fd-be9714280ff3  alexw@contoso.com    DeviceCode  true
+  acd6df42-10a9-4315-8928-53334f1c9d01  Contoso Application  Secret      false
+  ```
+
+  </TabItem>
+  <TabItem value="CSV">
+
+  ```csv
+  name,connectedAs,authType,active
+  028de82d-7fd9-476e-a9fd-be9714280ff3,alexw@contoso.com,DeviceCode,true
+  acd6df42-10a9-4315-8928-53334f1c9d01,Contoso Application,Secret,false
+  ```
+
+  </TabItem>
+  <TabItem value="Markdown">
+
+  ```md
+  # connection list
+
+  Date: 7/2/2023
+
+  ## 028de82d-7fd9-476e-a9fd-be9714280ff3
+
+  Property | Value
+  ---------|-------
+  name | 028de82d-7fd9-476e-a9fd-be9714280ff3
+  connectedAs | alexw@contoso.com
+  authType | DeviceCode
+  active | true
+
+  ## acd6df42-10a9-4315-8928-53334f1c9d01
+
+  Property | Value
+  ---------|-------
+  name | acd6df42-10a9-4315-8928-53334f1c9d01
+  connectedAs | Contoso Application
+  authType | Secret
+  active | false
+  ```
+
+  </TabItem>
+</Tabs>

package/docs/docs/cmd/connection/connection-remove.mdx

@@ -0,0 +1,45 @@
+import Global from '/docs/cmd/_global.mdx';
+
+# connection remove
+
+Remove the specified connection
+
+## Usage
+
+```sh
+m365 connection remove [options]
+```
+
+## Options
+
+```md definition-list
+`-n, --name <name>`
+: The name of the connection to remove.
+
+`-f, --force`
+: Don't prompt for confirmation to remove the connection.
+```
+
+<Global />
+
+## Remarks
+
+The value for `--name` can be found by running [m365 connection list](connection-list.mdx). 
+
+## Examples
+
+Remove an existing connection
+
+```sh
+m365 connection remove --name '0bb7cb89-7fae-4775-a01a-c372cc167371'
+```
+
+Remove an existing connection without prompting for confirmation
+
+```sh
+m365 connection remove --name '0bb7cb89-7fae-4775-a01a-c372cc167371' --force
+```
+
+## Response
+
+The command won't return a response on success.

package/docs/docs/cmd/connection/connection-set.mdx

@@ -0,0 +1,39 @@
+import Global from '/docs/cmd/_global.mdx';
+
+# connection set
+
+Rename the specified connection
+
+## Usage
+
+```sh
+m365 connection set [options]
+```
+
+## Options
+
+```md definition-list
+`-n, --name <name>`
+: The name of the connection to update.
+
+`--newName <newName>`
+: The new name of the connection.
+```
+
+<Global />
+
+## Remarks
+
+The value for `--name` can be found by running [m365 connection list](connection-list.mdx). You can update the name of a connection to any value to make switching connections easier. 
+
+## Examples
+
+Update an existing connection
+
+```sh
+m365 connection set --name '0bb7cb89-7fae-4775-a01a-c372cc167371' --newName 'myworkaccount'
+```
+
+## Response
+
+The command won't return a response on success.

package/docs/docs/cmd/connection/connection-use.mdx

@@ -0,0 +1,98 @@
+import Global from '/docs/cmd/_global.mdx';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+# connection use
+
+Activate the specified Microsoft 365 tenant connection
+
+## Usage
+
+```sh
+m365 connection use [options]
+```
+
+## Options
+
+```md definition-list
+`-n, --name <name>`
+: The name of the connection to switch to.
+```
+
+<Global />
+
+## Remarks
+
+The value for `--name` can be found by running [m365 connection list](connection-list.mdx). You can update the name of a connection by running [m365 connection set](connection-set.mdx). 
+
+## Examples
+
+Switch to a different connection
+
+```sh
+m365 connection use --name '6e70c8ea-571d-4daf-bc48-9e1b49ac3390'
+```
+
+Switch to another connection by a custom connection name
+
+```sh
+m365 connection use --name 'myworkaccount'
+```
+
+## Response
+
+<Tabs>
+  <TabItem value="JSON">
+
+  ```json
+  {
+    "connectedAs": "alexw@contoso.com",
+    "connectedName": "028de82d-7fd9-476e-a9fd-be9714280ff3",
+    "authType": "DeviceCode",
+    "appId": "31359c7f-bd7e-475c-86db-fdb8c937548e",
+    "appTenant": "common",
+    "cloudType": "Public"
+  }
+  ```
+
+  </TabItem>
+  <TabItem value="Text">
+
+  ```text
+  appId      : 31359c7f-bd7e-475c-86db-fdb8c937548e
+  appTenant  : common
+  authType   : DeviceCode
+  cloudType  : Public
+  connectionName : 028de82d-7fd9-476e-a9fd-be9714280ff3
+  connectedAs: alexw@contoso.com
+  ```
+
+  </TabItem>
+  <TabItem value="CSV">
+
+  ```csv
+  connectionName,connectedAs,authType,appId,appTenant,cloudType
+  alexw@contoso.com,028de82d-7fd9-476e-a9fd-be9714280ff3,DeviceCode,31359c7f-bd7e-475c-86db-fdb8c937548e,common,Public
+  ```
+
+  </TabItem>
+  <TabItem value="Markdown">
+
+  ```md
+  # connection use
+
+  Date: 7/2/2023
+
+  Property | Value
+  ---------|-------
+  connectedAs | alexw@contoso.com
+  connectionName | 028de82d-7fd9-476e-a9fd-be9714280ff3
+  authType | DeviceCode
+  appId | 31359c7f-bd7e-475c-86db-fdb8c937548e
+  appTenant | common
+  cloudType | Public
+  ```
+
+  </TabItem>
+</Tabs>
+

package/docs/docs/cmd/entra/administrativeunit/administrativeunit-member-add.mdx

@@ -1,6 +1,4 @@
 import Global from '/docs/cmd/_global.mdx';
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
 
 # entra administrativeunit member add
 
@@ -94,6 +92,10 @@ Add a single device specified by name to an administrative unit specified by nam
 m365 entra administrativeunit member add --administrativeUnitName 'Marketing Division' --deviceName 'JohnDoe-PC'
 ```
 
+## Response 
+
+The command won't return a response on success.
+
 ## More information
 
-- Administrative units: https://learn.microsoft.com/entra/identity/role-based-access-control/administrative-units
+- Administrative units: https://learn.microsoft.com/entra/identity/role-based-access-control/administrative-units

package/docs/docs/cmd/entra/administrativeunit/administrativeunit-member-remove.mdx

@@ -0,0 +1,107 @@
+import Global from '/docs/cmd/_global.mdx';
+
+# entra administrativeunit member remove
+
+Removes a member (user, group, or device) from an administrative unit
+
+## Usage
+
+```sh
+m365 entra administrativeunit member remove [options]
+```
+
+## options
+
+```md definition-list
+`-i, --id [id]`
+: The id of the member to be removed. Specify either `id`, `userId`, `userName`, `groupId`, `groupName`, `deviceId` or `deviceName`.
+
+`--userId [userId]`
+: The id of the user to be removed. Specify either `id`, `userId`, `userName`, `groupId`, `groupName`, `deviceId` or `deviceName`.
+
+`--userName [userName]`
+: The user principal name (UPN) of the user to be removed. Specify either `id`, `userId`, `userName`, `groupId`, `groupName`, `deviceId` or `deviceName`.
+
+`--groupId [groupId]`
+: The id of the group to be removed. Specify either `id`, `userId`, `userName`, `groupId`, `groupName`, `deviceId` or `deviceName`.
+
+`--groupName [groupName]`
+: The name of the group to be removed. Specify either `id`, `userId`, `userName`, `groupId`, `groupName`, `deviceId` or `deviceName`.
+
+`--deviceId [deviceId]`
+: The id of the device to be removed. Specify either `id`, `userId`, `userName`, `groupId`, `groupName`, `deviceId` or `deviceName`.
+
+`--deviceName [deviceName]`
+: The name of the device to be removed. Specify either `id`, `userId`, `userName`, `groupId`, `groupName`, `deviceId` or `deviceName`.
+
+`--administrativeUnitId [administrativeUnitId]`
+: The id of the administrative unit. Specify either `administrativeUnitId` or `administrativeUnitName` but not both.
+
+`--administrativeUnitName [administrativeUnitName]`
+: The name of the administrative unit. Specify either `administrativeUnitId` or `administrativeUnitName` but not both.
+
+`-f, --force`
+: Don't prompt for confirmation.
+```
+
+<Global />
+
+## Remarks
+
+:::info
+
+To use this command you must be either **Global Administrator** or **Privileged Role Administrator**.
+
+:::
+
+## Examples
+
+Remove a member specified by id from an administrative unit specified by id
+
+```sh
+m365 entra administrativeunit member remove --id 64131a70-beb9-4ccb-b590-4401e58446ec --administrativeUnitId 03c4c9dc-6f0c-4c4f-a4e6-0c9ed80f54c7
+```
+
+Remove a user specified by id from an administrative unit specified by id
+
+```sh
+m365 entra administrativeunit member remove --userId 64131a70-beb9-4ccb-b590-4401e58446ec --administrativeUnitId 03c4c9dc-6f0c-4c4f-a4e6-0c9ed80f54c7
+```
+
+Remove a group specified by id from an administrative unit specified by id
+
+```sh
+m365 entra administrativeunit member remove --groupId b2307a39-e878-458b-bc90-03bc578531d6 --administrativeUnitId 03c4c9dc-6f0c-4c4f-a4e6-0c9ed80f54c7
+```
+
+Remove a device specified by id from an administrative unit specified by id
+
+```sh
+m365 entra administrativeunit member remove --deviceId 810c84a8-4a9e-49e6-bf7d-12d183f40d01 --administrativeUnitId 03c4c9dc-6f0c-4c4f-a4e6-0c9ed80f54c7
+```
+
+Remove a user specified by UPN from an administrative unit specified by name
+
+```sh
+m365 entra administrativeunit member remove --userName john.doe@contoso.com --administrativeUnitName 'Marketing Division'
+```
+
+Remove a group specified by name from an administrative unit specified by id
+
+```sh
+m365 entra administrativeunit member remove --groupName 'Marketing Group' --administrativeUnitId 03c4c9dc-6f0c-4c4f-a4e6-0c9ed80f54c7
+```
+
+Remove a device specified by name from an administrative unit specified by name
+
+```sh
+m365 entra administrativeunit member remove --deviceName 'JohnDoe-PC' --administrativeUnitName 'Marketing Division'
+```
+
+## Response
+
+The command won't return a response on success
+
+## More information
+
+- [Administrative units](https://learn.microsoft.com/entra/identity/role-based-access-control/administrative-units)

package/docs/docs/cmd/entra/app/app-add.mdx

@@ -16,6 +16,7 @@ m365 entra app add [options]
 
 ```sh
 m365 aad app add [options]
+m365 entra appregistration add [options]
 ```
 
 ## Options
@@ -109,7 +110,7 @@ After creating the Entra app registration, this command returns the app ID and o
 
 If you want to store the information about the created Entra 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.
 
-When specifying `--grantAdminConsent` option, a service principal will be created for the app registration.
+When specifying `--grantAdminConsent` option, an enterprise application will be created for the app registration.
 
 ## Examples