[tjovicic]

Explaining how to connect to a datastore using EntraID

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
documentation	Ready	Preview	Oct 19, 2026 10:33am UTC

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can import rules and skills only from the repositories your team follows

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Document Microsoft Entra ID data store connections

📝 Documentation 🕐 10-20 Minutes

AI Description

• Consolidate Entra ID setup guidance into the data store documentation for a complete connection
 workflow.
• Explain identity-based ACL rules and token authentication with Azure CLI and Redis CLI.
• Remove the obsolete identity-provider page and its category listing.

Diagram

graph TD
  A["Azure app"] --> B["Identity provider"] --> C["Entra data store"] --> D["OID ACL rule"] --> F["Redis CLI connection"]
  A --> E["Scoped access token"] --> F

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Dedicated Entra data store guide

• ➕ Easier to find as a standalone guide
• ➕ Leaves the general data store page shorter
• ➖ Splits setup from the data store instructions it depends on
• ➖ Requires cross-links to keep the workflow connected

Recommendation: Keep the integrated walkthrough for now: Azure registration, store authorization, and connection form one short workflow. Consider a dedicated guide if additional Entra authentication scenarios make this section substantially longer.

Files changed (2) +58 / -1

Documentation (2) +58 / -1

_category_.ymlRemove identity providers from the access category summary +1/-1

Remove identity providers from the access category summary

• Removes identity providers from the generated category description after the standalone page is deleted.

docs/cloud/access-permissions/category.yml

datastores.mdAdd an end-to-end Entra ID data store guide +57/-0

Add an end-to-end Entra ID data store guide

• Moves Azure application and Dragonfly Cloud identity-provider setup into the data store page. Adds instructions for selecting Entra ID, authorizing an object ID with an ACL rule, and connecting over TLS using an Azure CLI token.

docs/cloud/datastores.md

[Copilot]

🟡 Changes recommended

The user-token connection example omits delegated-scope and Azure CLI authorization prerequisites.

1 open issue

• Azure CLI user sign-in lacks delegated scope and consent setup · New

What changed in this PR

Consolidates Microsoft Entra ID integration guidance into the Dragonfly Cloud datastore documentation.

Changes:

• Moves Azure and identity-provider setup into the datastore guide.
• Adds ACL configuration and token-based connection instructions.
• Updates the Access & Permissions category description.

File	Description
docs/​cloud/​datastores.md	Adds Entra setup, ACL, and connection guidance.
docs/​cloud/​access-permissions/​identity-providers.md	Removes the standalone guide.
docs/​cloud/​access-permissions/​_category_.yml	Removes identity providers from the category description.

_{Review effort: Balanced}

[moredure]

lgtm