* docs(azure-apim): reflect Settings tab + cascade-delete + audience-uniqueness
Three updates after merging the per-user identity feature to production:
1. Dashboard navigation: Entra cards moved from the Overview tab to a
conditional Settings tab (only visible for enterprise teamspaces or
active trials). Update Part 4 and the troubleshooting section.
2. Cascade-delete: clicking Remove on the Microsoft Entra ID card now
removes both the tenant configuration AND all provisioned users in a
single step. Add a note so admins know not to use Remove for
single-user revocation.
3. Audience uniqueness: each MCP API app (audience GUID) can be claimed
by one teamspace at a time. Document the failure mode and how to
resolve it, since hitting it from a fresh setup is easy.
* docs(azure-apim): add Part 6 — smoke test the gateway from CLI
Walks through pre-authorizing Azure CLI on the Gateway app's scope and
running an `az account get-access-token` + curl against APIM end-to-end.
Lets admins validate the full OBO flow before pointing real MCP clients
at the gateway.
Renumber the original "Connect an MCP client" to Part 7.
* docs(enterprise): add Azure APIM deployment guide
Step-by-step guide for deploying Context7 behind Azure API Management
with Microsoft Entra ID per-user authentication via On-Behalf-Of (OBO)
token exchange. Covers APIM provisioning, Entra app registrations,
policy wiring, OAuth discovery surfaces, and connecting MCP clients
(VS Code Copilot, Cursor) through the gateway.
* docs(azure-apim): cover user pre-provisioning + fix variable typo
- Restructure Part 4 into two steps: tenant config + pre-provisioning
users via the new dashboard card. Calls out that Context7 rejects
unmapped oids — there is no auto-provisioning.
- Add troubleshooting entry for the unmapped-user 401 (most common
failure once tenant config is correct).
- Fix \$APIM_NAME → \$APIM typo in the OAuth proxy provisioning
commands; the rest of the doc uses \$APIM so the OAuth proxy
commands would have failed as written.
The single deployment.mdx page implied Kubernetes-only deployment. Split it into
a deployment/ folder with separate Docker and Kubernetes guides, and simplify the
on-premise getting started page to link to them via Mintlify cards.
New deployment.mdx page under the On-Premise section covering
StatefulSet, Service, Ingress manifests, registry auth, networking
requirements, operations, and troubleshooting for K8s deployments.
* Add on-premise deployment docs
Hidden page covering what's included, setup steps, configuration
reference, MCP client connection, and architecture diagram.
* Update on-premise docs: switch from tar.gz to GHCR registry pull
Replace curl+docker load approach with standard docker login + docker pull
using a license-gated registry token from context7.com.
* Fix on-premise docs: separate auth step, clarify docker compose pull
- Split into distinct "Authenticate" and "Configure and start" steps
- Remove redundant docker pull (docker compose up -d handles it)
- Add driver: local to volumes declaration
- Clarify that docker login credentials persist for docker compose
* docs: mention docker pull as alternative to docker compose pull
* docs: use -p flag instead of --password-stdin for docker login
* Move on-premise docs to enterprise/, add configuration details
- Move on-premise.mdx from docs root to docs/enterprise/
- Add setup wizard documentation
- Add AI provider settings with OpenRouter and local model examples
- Add embedding settings with incompatibility warning
- Add access control section with permission toggles
- Add volume persistence warning
- Remove env vars for AI/git config (now UI-configured)
* Docs: clarify git tokens, add health check example, group operations
* Docs: extract LICENSE_KEY variable for easier configuration
Fahreddin Özcan