Currently we do have a User Guide page for login where we talks about logging in using Custom AAD App and Client Secret . Over there, the approach is to add TenantId and AppId as Environment Variable. The use case which I am thinking of is to have a one time execution kind of scenario where the users may not need to setup environment variable since they might be using the CLI in the Device Flow approach otherwise.
What I am suggesting it to
- Add a section in the Login User Guide which talks something like Login with Client Secret without setting Environment Variable (I know the heading length is on a higher end. Couldn't get anything better)
- Add one more example in the login page for an example like Logging in using Custom AAD App and Client Secret for a specific tenant which may have example like
m365 login authType secret --appId e999f999-87ce-4a1a-ba80-a5101e48e0db --tenant 999efa99-57fa-40c7-b7cc-e96dc3e5780c --secret SUPERSECRET
Currently we do have a User Guide page for login where we talks about logging in using Custom AAD App and Client Secret . Over there, the approach is to add
TenantIdandAppIdas Environment Variable. The use case which I am thinking of is to have a one time execution kind of scenario where the users may not need to setup environment variable since they might be using the CLI in the Device Flow approach otherwise.What I am suggesting it to
m365 login authType secret --appId e999f999-87ce-4a1a-ba80-a5101e48e0db --tenant 999efa99-57fa-40c7-b7cc-e96dc3e5780c --secret SUPERSECRET