mirror of
https://github.com/hanzoai/kms.git
synced 2026-11-03 01:10:24 +00:00
zeekay
db49f40b8e
Public-facing docs, metadata, and branding: - README.md: remove fork attribution, rebrand intro - package.json: clean description - CONTRIBUTING.md, SECURITY.md: remove Infisical mentions - LLM.md: update image name, remove fork language - docs/docs.json: rebrand name, nav labels, social links, footer URLs - company/ handbook & docs: rebrand all Infisical mentions - .env.migration.example: use hanzokms credentials - flake.nix: update description, remove infisical package - .github/ISSUE_TEMPLATE/config.yml: fix broken ghcr.io URLs - docs/ (24 files): rebrand prose, mermaid diagrams, API URLs - docs/Dockerfile: update spec fetch URL Removed upstream assets: - img/infisical_github_repo.png, infisical_github_repo2.png - .github/images/star-infisical.gif - .github/images/.!35663!deploy-to-aws.png (corrupted empty) NOT changed (would break code/legal): - LICENSE (MIT copyright must stay) - backend/src/ee/LICENSE.md (upstream enterprise license) - backend/package.json (@infisical/* npm deps) - Dockerfiles (apt-get install infisical CLI) - env var names (INFISICAL_TOKEN, INF_APP_CONNECTION_*) - docs.json page paths (require file renames) - frontend/dist/locales (compiled translation keys)
61 lines
2.7 KiB
Plaintext
61 lines
2.7 KiB
Plaintext
---
|
|
title: "Azure DNS Connection"
|
|
description: "Learn how to configure an Azure DNS Connection for KMS."
|
|
---
|
|
|
|
KMS supports connecting to Azure DNS using a Service Principal with Client Secrets for secure access to manage DNS records in your Azure DNS zones.
|
|
|
|
<Accordion title="Client Secret Authentication">
|
|
To use client secret authentication, ensure your Azure Service Principal has the required permissions to manage DNS records in your Azure DNS Zone.
|
|
|
|
**Prerequisites:**
|
|
- Set up Azure and have an existing DNS Zone.
|
|
- An Azure Service Principal (App Registration) with a Client Secret.
|
|
|
|
<Steps>
|
|
<Step title="Navigate to your DNS Zone">
|
|
In the Azure Portal, navigate to your DNS Zone that you want to use for ACME DNS validation. Click on **Access control (IAM)** in the left sidebar, then click **Add** > **Add role assignment**.
|
|
|
|
|
|
</Step>
|
|
<Step title="Assign DNS Zone Contributor Role">
|
|
Search for and select the **DNS Zone Contributor** role, then click **Next**.
|
|
|
|
|
|
</Step>
|
|
<Step title="Select your Service Principal">
|
|
Click **Select members**, search for your App Registration (Service Principal), select it, and click **Select**.
|
|
|
|
|
|
|
|
Click **Review + assign** to complete the role assignment.
|
|
</Step>
|
|
</Steps>
|
|
</Accordion>
|
|
|
|
## Setup Azure DNS Connection in KMS
|
|
|
|
<Steps>
|
|
<Step title="Navigate to App Connections">
|
|
Navigate to the **App Connections** page in the desired project.
|
|
|
|
</Step>
|
|
<Step title="Add Connection">
|
|
Select the **Azure DNS Connection** option from the connection options modal.
|
|
|
|
</Step>
|
|
<Step title="Create Connection">
|
|
Fill in the **Tenant ID**, **Client ID**, **Client Secret**, and **Subscription ID** fields with the credentials from your Azure Service Principal.
|
|
|
|
|
|
|
|
<Tip>
|
|
You can find your **Subscription ID** in the Azure Portal under **Subscriptions**. The **Tenant ID** and **Client ID** can be found in your App Registration's **Overview** page.
|
|
</Tip>
|
|
</Step>
|
|
<Step title="Connection Created">
|
|
Your **Azure DNS Connection** is now available for use in your KMS projects.
|
|
|
|
</Step>
|
|
</Steps>
|