Can't use Microsoft365R because the app is blocked. What can I do?

[**[This information is also in the authentication vignette]**](https://cran.r-project.org/web/packages/Microsoft365R/vignettes/auth.html)

Most orgs will require an admin to grant consent for third-party apps to access tenant data. The **recommended solution** is to let your admin know about this package and wait for them to approve it. See **[app_registration.md](https://github.com/Azure/Microsoft365R/blob/master/inst/app_registration.md)** for the details on the app registration and default permissions requested.

Here are some workarounds if you can't wait:

- By setting the R option `microsoft365r_use_cli_app_id` to a non-NULL value, authentication will be done using the app ID for the [CLI for Microsoft 365](https://pnp.github.io/cli-microsoft365/). Technically this app still requires admin approval, but it is in widespread use and so may already be allowed in your organisation.
- You can authenticate using the [Azure CLI's](https://docs.microsoft.com/en-us/cli/azure/what-is-azure-cli) app ID: `04b07795-8ddb-461a-bbee-02f9e1bf7b46`. This isn't meant for use with MS 365, so functionality is limited. However, it will let you access Sharepoint drives and lists.

Be warned that these solutions may draw the attention of your admin!

Start with the authentication vignette and inst/app_registration.md, which the issue links, and compare their explanation of blocked-app consent with the listed CLI workarounds. Done means the supported admin-consent path and workaround limitations are clearly documented in the relevant authentication guidance.

Written by the indexing model from the issue text.