diff --git a/docs/documentation/platform/dynamic-secrets/azure-entra-id.mdx b/docs/documentation/platform/dynamic-secrets/azure-entra-id.mdx
index cd1d30fb0..8a71772b1 100644
--- a/docs/documentation/platform/dynamic-secrets/azure-entra-id.mdx
+++ b/docs/documentation/platform/dynamic-secrets/azure-entra-id.mdx
@@ -80,10 +80,6 @@ Click on Add assignments. Search for the application name you created and select
-
- For testing purposes, you can also use a highly privileged role like `superuser`, that will have full control over the cluster. This is not recommended in production environments following the principle of least privilege.
-
-
## Set up Dynamic Secrets with Azure Entra ID
@@ -93,12 +89,12 @@ Click on Add assignments. Search for the application name you created and select
-
- 
+
+ 
-
- Name by which you want the secret to be referenced
+
+ Prefix for the secrets to be created
@@ -109,54 +105,27 @@ Click on Add assignments. Search for the application name you created and select
Maximum time-to-live for a generated secret.
-
- Your Elasticsearch host. This is the endpoint that your instance runs on. _(Example: https://your-cluster-ip)_
+
+ The Tenant ID of your Azure Entra ID account.
-
- The port that your Elasticsearch instance is running on. _(Example: 9200)_
+
+ The Application ID of the application you created in Azure Entra ID.
-
- The roles that the new user that is created when a lease is provisioned will be assigned to. This is a required field. This defaults to `superuser`, which is highly privileged. It is recommended to create a new role with the least privileges required for the lease.
-
-
-
- Select the authentication method you want to use to connect to your Elasticsearch instance.
+
+ The Client Secret of the application you created in Azure Entra ID.
-
- The username of the user that will be used to provision new dynamic secret leases. Only required if you selected the `Username/Password` authentication method.
+
+ Multi select list of users to generate secrets for.
-
- The password of the user that will be used to provision new dynamic secret leases. Only required if you selected the `Username/Password` authentication method.
-
-
-
- The ID of the API key that will be used to provision new dynamic secret leases. Only required if you selected the `API Key` authentication method.
-
-
-
- The API key that will be used to provision new dynamic secret leases. Only required if you selected the `API Key` authentication method.
-
-
-
- A CA may be required if your DB requires it for incoming connections. This is often the case when connecting to a managed service.
-
-
- 
-
-
- After submitting the form, you will see a dynamic secret created in the dashboard.
-
-
- If this step fails, you may have to add the CA certificate.
-
-
+ After submitting the form, you will see a dynamic secrets for each user created in the dashboard.
+
Once you've successfully configured the dynamic secret, you're ready to generate on-demand credentials.
To do this, simply click on the 'Generate' button which appears when hovering over the dynamic secret item.
@@ -176,7 +145,7 @@ Click on Add assignments. Search for the application name you created and select
Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
- 
+ 
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-lease.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-lease.png
new file mode 100644
index 000000000..4740062db
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-lease.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-modal.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-modal.png
new file mode 100644
index 000000000..481c78923
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-modal.png differ