diff --git a/docs/documentation/platform/dynamic-secrets/azure-entra-id.mdx b/docs/documentation/platform/dynamic-secrets/azure-entra-id.mdx
new file mode 100644
index 000000000..cd1d30fb0
--- /dev/null
+++ b/docs/documentation/platform/dynamic-secrets/azure-entra-id.mdx
@@ -0,0 +1,195 @@
+---
+title: "Azure Entra Id"
+description: "Learn how to dynamically generate Azure Entra Id user credentials."
+---
+
+The Infisical Azure Entra Id dynamic secret allows you to generate Azure Entra Id credentials on demand based on configured role.
+
+## Prerequisites
+
+
+
+Login to [Microsoft Entra ID](https://entra.microsoft.com/)
+
+
+
+Go to Overview, Copy and store `Tenant Id`
+
+
+
+
+Go to Applications > App registrations. Click on New Registration.
+
+
+
+
+Enter an application name. Click Register.
+
+
+
+Copy and store `Application Id`.
+
+
+
+
+Go to Clients and Secrets. Click on New Client Secret.
+
+
+
+Enter a description, select expiry and click Add.
+
+
+
+Copy and store `Client Secret` value.
+
+
+
+
+Go to API Permissions. Click on Add a permission.
+
+
+
+
+Click on Microsoft Graph.
+
+
+
+
+Click on Application Permissions. Search and select `User.ReadWrite.All` and click Add permissions.
+
+
+
+
+Click on Grant admin consent for app. Click yes to confirm.
+
+
+
+
+Go to Dashboard. Click on show more.
+
+
+
+
+Click on Roles & admins. Search for User Administrator and click on it.
+
+
+
+
+Click on Add assignments. Search for the application name you created and select it. Click on Add.
+
+
+
+
+
+ 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
+
+
+
+ Open the Secret Overview dashboard and select the environment in which you would like to add a dynamic secret.
+
+
+ 
+
+
+ 
+
+
+
+ Name by which you want the secret to be referenced
+
+
+
+ Default time-to-live for a generated secret (it is possible to modify this value when a secret is generate)
+
+
+
+ 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 port that your Elasticsearch instance is running on. _(Example: 9200)_
+
+
+
+ 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 username of the user that will be used to provision new dynamic secret leases. Only required if you selected the `Username/Password` authentication method.
+
+
+
+ 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.
+
+
+
+
+ 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.
+ Alternatively, you can initiate the creation of a new lease by selecting 'New Lease' from the dynamic secret lease list section.
+
+ 
+ 
+
+ When generating these secrets, it's important to specify a Time-to-Live (TTL) duration. This will dictate how long the credentials are valid for.
+
+ 
+
+
+ Ensure that the TTL for the lease fall within the maximum TTL defined when configuring the dynamic secret.
+
+
+
+ Once you click the `Submit` button, a new secret lease will be generated and the credentials from it will be shown to you.
+
+ 
+
+
+
+## Audit or Revoke Leases
+Once you have created one or more leases, you will be able to access them by clicking on the respective dynamic secret item on the dashboard.
+This will allow you see the expiration time of the lease or delete a lease before it's set time to live.
+
+
+
+## Renew Leases
+To extend the life of the generated dynamic secret leases past its initial time to live, simply click on the **Renew** as illustrated below.
+
+
+
+ Lease renewals cannot exceed the maximum TTL set when configuring the dynamic secret
+
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-add-assignments.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-add-assignments.png
new file mode 100644
index 000000000..561639de0
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-add-assignments.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-add-client-secret.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-add-client-secret.png
new file mode 100644
index 000000000..358fc53c1
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-add-client-secret.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-add-permission.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-add-permission.png
new file mode 100644
index 000000000..20614f9dc
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-add-permission.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-admin-consent.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-admin-consent.png
new file mode 100644
index 000000000..5c8102450
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-admin-consent.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-copy-app-id.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-copy-app-id.png
new file mode 100644
index 000000000..aa36ee39d
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-copy-app-id.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-new-registration.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-new-registration.png
new file mode 100644
index 000000000..285df9d77
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-new-registration.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-select-graph.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-select-graph.png
new file mode 100644
index 000000000..98f23c084
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-select-graph.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-select-perms.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-select-perms.png
new file mode 100644
index 000000000..45abaa738
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-select-perms.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-show-more.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-show-more.png
new file mode 100644
index 000000000..df4dc9567
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-show-more.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-tenant-id.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-tenant-id.png
new file mode 100644
index 000000000..5b0cb4763
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-tenant-id.png differ
diff --git a/docs/images/platform/dynamic-secrets/dynamic-secret-ad-user-admin.png b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-user-admin.png
new file mode 100644
index 000000000..dfc1deadd
Binary files /dev/null and b/docs/images/platform/dynamic-secrets/dynamic-secret-ad-user-admin.png differ
diff --git a/docs/mint.json b/docs/mint.json
index 60f7bbbcb..2fbce096d 100644
--- a/docs/mint.json
+++ b/docs/mint.json
@@ -167,7 +167,8 @@
"documentation/platform/dynamic-secrets/rabbit-mq",
"documentation/platform/dynamic-secrets/aws-iam",
"documentation/platform/dynamic-secrets/mongo-atlas",
- "documentation/platform/dynamic-secrets/mongo-db"
+ "documentation/platform/dynamic-secrets/mongo-db",
+ "documentation/platform/dynamic-secrets/azure-entra-id"
]
},
{