Skip to content

Commit

Permalink
doc: Update errors.md
Browse files Browse the repository at this point in the history
  • Loading branch information
RogerSelwyn committed May 5, 2024
1 parent 28d3299 commit 041c1a8
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion docs/errors.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,9 @@ nav_order: 19
* Where this error mentions `Presence.Read` or `Chat.Read` it probably means you have tried to configure a Teams Presence or Chat sensor when your account is a Personal Account (such as @outlook.com)
* For other items, it means you have changed your configuration to require new permissions. You will likely need to delete your token and reauthenticate. Please check the [permissions page](./permissions.md) for more details.

* **The user could not be authenticated as the grant is expired. The user must sign in again.**
* Create a new secret and update your O365 configuration. Then delete your token and reauthenticate. Please check the [permissions page](./permissions.md) for more details.

* **Client secret expired for account: xxxxxxxx. Create new client id in Azure App.**
* The Client Secret on your Azure App has expired. Create a new secret and update your O365 configuration.

Expand All @@ -35,4 +38,4 @@ Validate your Azure permissions match those required as detailed on the [permiss
**_Please note that any changes made to your Azure app settings takes a few minutes to propagate. Please wait around 5 minutes between changes to your settings and any auth attempts from Home Assistant._**

# Installation issues
* If your installation does not complete authentication, or the sensors are not created, please go back and ensure you have accurately followed the steps detailed, also look in the logs to see if there are any errors.
* If your installation does not complete authentication, or the sensors are not created, please go back and ensure you have accurately followed the steps detailed, also look in the logs to see if there are any errors.

0 comments on commit 041c1a8

Please sign in to comment.