diff --git a/docs/configuration.md b/docs/configuration.md
index 8201276..42ffb70 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -17,12 +17,13 @@ You don't have to configure other settings in most cases, as they have secure de
## Provider Configurations
Here are some documentation links for specific providers that you may want to follow:
-| 
| 
| 
|
-|:-----------------------------------------------------------------------------------------:|:-------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------:|
-| [Authentik](./provider-configurations/authentik.md) | [Authelia](./provider-configurations/authelia.md) | [Pocket ID](./provider-configurations/pocket-id.md) |
+* [Authentik](./provider-configurations/authentik.md)
+* [Authelia](./provider-configurations/authelia.md)
+* [Pocket ID](./provider-configurations/pocket-id.md)
+* [Kanidm](./provider-configurations/kanidm.md)
+* [Microsoft Entra ID](./provider-configurations/microsoft-entra.md)
-
-Are you using another provider? Another user might have added configuration instructions here: [Other providers](./provider-configurations/other.md)
+_Missing a provider? Submit your guide using a PR._
## Common Configurations
### Configuring Client Secret
@@ -136,4 +137,4 @@ Here's a table of all options that you can set:
| `roles.admin` | `string` | No | `admins` | Group name to require for users to get the 'admin' role in Home Assistant. Defaults to 'admins', the default group name for admins in Authentik. Doesn't do anything if no groups claim is found in your token. |
| `roles.user` | `string` | No | | Group name to require for users to get the 'user' role in Home Assistant. Defaults to giving all users this role, unless configured. |
| `network.tls_verify` | `boolean` | No | `true` | Verify TLS certificate. You may want to set this set to `false` when testing locally. |
-| `network.tls_ca_path` | `string` | No | | Path to file containing a private certificate authority chain. |
\ No newline at end of file
+| `network.tls_ca_path` | `string` | No | | Path to file containing a private certificate authority chain. |
diff --git a/docs/provider-configurations/other.md b/docs/provider-configurations/microsoft-entra.md
similarity index 94%
rename from docs/provider-configurations/other.md
rename to docs/provider-configurations/microsoft-entra.md
index f3dba03..eadb745 100644
--- a/docs/provider-configurations/other.md
+++ b/docs/provider-configurations/microsoft-entra.md
@@ -1,7 +1,4 @@
-# Other providers
-Under construction.
-
-## Microsoft Entra ID
+# Microsoft Entra ID
> [!WARNING]
> Microsoft Entra ID does not support public clients that are not Single Page Applications (SPA's). Therefore, you will have to use a client secret.
@@ -27,4 +24,4 @@ auth_oidc:
```
> [!CAUTION]
-> Be careful! Configuring Entra ID wrong may leave your Home Assistant install open for anyone with a Microsoft account. Please use "Single tenant" account types only. Do not enable "Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant)" or personal account modes without enabling the mode to only allow specific accounts first!
\ No newline at end of file
+> Be careful! Configuring Entra ID wrong may leave your Home Assistant install open for anyone with a Microsoft account. Please use "Single tenant" account types only. Do not enable "Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant)" or personal account modes without enabling the mode to only allow specific accounts first!
diff --git a/docs/usage.md b/docs/usage.md
index 9b43f8c..65401c7 100644
--- a/docs/usage.md
+++ b/docs/usage.md
@@ -9,7 +9,7 @@ Install the integration through [HACS](https://hacs.xyz/). You can add it automa
### Step 2: Configuration of the integration
-The integration is currently configurable through YAML only. See the [Configuration Guide](./docs/configuration.md) for more details or pick your OIDC provider below:
+The integration is currently configurable through YAML only. See the [Configuration Guide](./configuration.md) for more details or pick your OIDC provider below (additional providers are available in the Configuration Guide):
| | | |
|:-----------------------------------------------------------------------------------------:|:-------------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------------:|
@@ -81,4 +81,4 @@ You can link the user directly to one of these following URLs:
For a seamless user experience, configure a new domain on your proxy to redirect to the `/auth/oidc/welcome` path or configure that path on your homelab dashboard or in your OIDC provider (such as in the app settings in Authentik). Users will then always start on the OIDC welcome page, which will allow them to visit the dashboard if they are already logged in.
-*Note: do not replace the standard path with a redirect to the OIDC screen. This breaks login with code.*
\ No newline at end of file
+*Note: do not replace the standard path with a redirect to the OIDC screen. This breaks login with code.*