We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
m365 cli app doctor
Verifies the configuration of the custom app reg for use with CLI
-i, --appId [appId]
--objectId [objectId]
-n, --name [name]
Verify the configuration of the custom app reg, specified using the app's client ID
m365 cli app doctor --appId dfd526d5-7367-4f78-bfc7-48a5434d7276
Verify the configuration of the custom app reg, specified using the app's object ID
m365 cli app doctor --objectId dfd526d5-7367-4f78-bfc7-48a5434d7276
m365 cli app doctor --name "My custom app"
n/a
The command retrieves information about the specified app reg and performs the following checks:
The command prints a list of checks with an x or a v when it passed, similarly to other doctor commands.
The text was updated successfully, but these errors were encountered:
Awesome suggestion, nothing to add. Let's open it up!
Sorry, something went wrong.
No branches or pull requests
Usage
m365 cli app doctor
Description
Verifies the configuration of the custom app reg for use with CLI
Options
-i, --appId [appId]
--objectId [objectId]
-n, --name [name]
Examples
Verify the configuration of the custom app reg, specified using the app's client ID
Verify the configuration of the custom app reg, specified using the app's object ID
Verify the configuration of the custom app reg, specified using the app's object ID
m365 cli app doctor --name "My custom app"
Default properties
n/a
Additional Info
The command retrieves information about the specified app reg and performs the following checks:
The command prints a list of checks with an x or a v when it passed, similarly to other doctor commands.
The text was updated successfully, but these errors were encountered: