## Summary **Batch B of Phase 3** of the H1 → front-matter migration (`DOCS-484`; parent `DOCS-477`), the editorial follow-up to Batch A (#28030). For the **124** hand-authored pages whose leading body H1 differed from the manifest nav label, this promotes the richer body H1 to the front-matter **page title** and drops the duplicate H1, while keeping the short manifest **label** as the sidebar entry. Policy agreed with the docs owner: - Short sidebar labels win. Duplicate sidebar labels are acceptable. - Identical **page titles** across two pages are not. On a collision, rename the non-generated page's title. ## Page-title collisions resolved Promoting the H1 created 4 page-title collisions; each is disambiguated by renaming the non-generated / secondary page (sidebar labels left unchanged): | page | sidebar label | body H1 | → page title | |------|---------------|---------|--------------| | `install/index.md` | Install | Installing Coder | **Install Coder in your infrastructure** | | `install/cli.md` | Coder CLI | Installing Coder | **Install the Coder CLI** | | `ai-gateway/clients/jetbrains.md` | JetBrains | JetBrains IDEs | **JetBrains** | | `workspace-access/web-ides.md` | Web IDEs and Coder Apps | Web IDEs | Web IDEs *(kept — primary user guide)* | | `extending-templates/web-ides.md` | Web IDEs and Coder Apps | Web IDEs | **Web IDEs in templates** | | `workspace-management.md` | Workspace Management | Workspaces | **Manage workspaces** *(vs generated `api/workspaces.md`)* | These titles are the only non-mechanical editorial calls in this PR. ## Deliberately excluded: generated pages `admin/security/audit-logs.md` and `admin/setup/configuration-reference.md` are `make gen` outputs (`auditdocgen` / `configdocgen`) that Phase 2 did **not** update, so a hand-added title would be reverted on the next generation. They're excluded here and need their generators taught to emit front matter first (Phase 2 pattern), tracked as `DOCS-631`. Batch A (#28030) had the same issue for three other generated pages; it has been corrected there too. ## Verification AI was the primary author of this PR (see disclosure below); per the [AI Contribution Guidelines](https://coder.com/docs/about/contributing/AI_CONTRIBUTING) here is the manual verification. - Promote = set front-matter `title` to the body H1 (or the disambiguated title above) and remove that one duplicate H1. No other body prose is reflowed. - Every added front-matter block parses as YAML; all files pass `pnpm check-docs` (markdownlint-cli2 + table formatter): `Summary: 0 error(s)`. - Removing the H1 orphaned one in-page fragment (`[MCP](#mcp)` in `ai-gateway/mcp.md`), now repointed. A cross-file fragment audit into the retitled pages found no real breakage. Anchor-change note Unlike Batch A (title unchanged, a rendered no-op), Batch B changes each page's effective title from the manifest label to the body H1, so the rendered H1 **anchor slug changes**. An audit of cross-file `.md#fragment` links into these pages surfaced no links that break as a result (the only hits were false positives against a still-present `## TLS & Reverse Proxy` heading). Same-file fragments are enforced by markdownlint MD051, which is green. ## Title casing (follow-up, DOCS-742) A follow-up commit puts the promoted titles into sentence case and removes leading gerunds (for example, `Managing workspace schedules` → `Manage workspace schedules`): 57 of the 120 titles changed, the other 63 were already compliant. Proper nouns and branded names (Coder Validated Architecture, JetBrains, File Browser, Dev Containers, Island), acronyms (API, CLI, IDE, MCP, OIDC, URL, UI, CI/CD), the Premium license tier, and maturity labels (Beta, Experimental) are preserved. The four `Nk-users` pages become `Reference architecture: up to N users` (lowercase, matching the CVA landing page's own usage); the CVA landing page keeps its branded title. `pnpm check-docs`: `Summary: 0 error(s)`. Linear: DOCS-484, DOCS-742 > This PR was created with AI assistance (Coder Agents).
4.4 KiB
title
| title |
|---|
| Federate Coder's control plane to Azure |
This guide will walkthrough how to authenticate a Coder Provisioner to Microsoft Azure, using a Service Principal with a client certificate. You can use this guide for authenticating Coder to Azure, regardless of where Coder is run, either on-premise or in a non-Azure cloud. This method is one of several recommended by Terraform.
Step 1: Generate Client Certificate & PKCS bundle
We'll need to create the certificate Coder will use for authentication. Run the below command to generate a private key and self-signed certificate:
openssl req -subj '/CN=myclientcertificate/O=MyCompany, Inc./ST=CA/C=US' \
-new -newkey rsa:4096 -sha256 -days 730 -nodes -x509 -keyout client.key -out client.crt
Next, generate a .pfx file to be used by Coder's Provisioner to authenticate
the AzureRM provider:
openssl pkcs12 -export -password pass:"Pa55w0rd123" -out client.pfx -inkey client.key -in client.crt
Step 2: Create Azure Application & Service Principal
Navigate to the Azure portal, and into the Microsoft Entra ID section. Select the App Registration blade, and register a new application. Fill in the following fields:
- Name: this is a friendly identifier and can be anything (e.g. "Coder")
- Supported Account Types: - set to "Accounts in this organizational directory only (single-tenant)"
The Redirect URI field does not need to be set in this case. Take note of
the Application (client) ID and Directory (tenant) ID values, which will be
used by Coder.
Step 3: Assign Client Certificate to the Azure Application
To upload the certificate we created in Step 1, select Certificates &
secrets on the left-hand side, and select Upload Certificate. Upload the
public key file, which is service-principal.crt from the example above.
Step 4: Set Permissions on the Service Principal
Now that the Application is created in Microsoft Entra ID, we need to assign permissions to the Service Principal so it can provision Azure resources for Coder users. Navigate to the Subscriptions blade in the Azure Portal, select the Subscription > Access Control (IAM) > Add > Add role assignment.
Set the Role that grants the appropriate permissions to create the Azure
resources you need for your Coder workspaces. Contributor will provide
Read/Write on all Subscription resources. For more information on the available
roles, see the
Microsoft documentation.
Step 5: Configure Coder to use the Client Certificate
Now that the client certificate is uploaded to Azure, we need to mount the
certificate files into the Coder deployment. If running Coder on Kubernetes, you
will need to create the .pfx file as a Kubernetes secret, and mount it into
the Helm chart.
Run the below command to create the secret:
kubectl create secret generic -n coder azure-client-cert-secret --from-file=client.pfx=/path/to/your/client.pfx
In addition, create secrets for each of the following values from your Azure Application:
- Client ID
- Tenant ID
- Subscription ID
- Certificate password
Next, set the following values in Coder's Helm chart:
coder:
env:
- name: ARM_CLIENT_ID
valueFrom:
secretKeyRef:
key: id
name: arm-client-id
- name: ARM_CLIENT_CERTIFICATE_PATH
value: /home/coder/az/
- name: ARM_CLIENT_CERTIFICATE_PASSWORD
valueFrom:
secretKeyRef:
key: password
name: arm-client-cert-password
- name: ARM_TENANT_ID
valueFrom:
secretKeyRef:
key: id
name: arm-tenant-id
- name: ARM_SUBSCRIPTION_ID
valueFrom:
secretKeyRef:
key: id
name: arm-subscription-id
volumes:
- name: "azure-client-cert"
secret:
secretName: "azure-client-cert-secret"
volumeMounts:
- name: "azure-client-cert"
mountPath: "/home/coder/az/"
readOnly: true
Upgrade the Coder deployment using the following helm command:
helm upgrade coder coder-v2/coder -n coder -f values.yaml