Skip to content

[reorg fix] [DOCS-15112] Document Azure Secretless Auth setup and migration - #39073

Open
jhgilbert wants to merge 11 commits into
masterfrom
reorg-fix/pr-38328
Open

[reorg fix] [DOCS-15112] Document Azure Secretless Auth setup and migration#39073
jhgilbert wants to merge 11 commits into
masterfrom
reorg-fix/pr-38328

Conversation

@jhgilbert

Copy link
Copy Markdown
Contributor

🤖 Auto-generated fix for #38328.

@buraizu — the docs repo reorg created merge conflicts in your PR #38328. This is an auto-generated replacement with the file paths fixed; please use it instead of the original.

This PR replays the commits from #38328 with file paths translated to the post-reorg hugo/ layout. The original commits are preserved — same messages and authorship.

The original PR (#38328) will be closed in favor of this one.

Next steps:

  1. Verify that this PR looks correct in the browser.
  2. Remove the WORK IN PROGRESS label from this PR.
  3. Wait for the standard docs team approval before merging. Optionally, you can check the 'ready for merge' checkbox below if you would like the docs team to merge it for you.
  • Ready for merge

Original PR description:

What does this PR do? What is the motivation?

Fixes DOCS-15112

Documents Azure Secretless Auth (currently in Preview) on the Getting Started with Azure page and cross-links the migration flow from two Azure guides:

  • Getting Started with Azure — adds an "Authentication methods" section comparing Secretless Auth and Client Secret, adds the Authentication Method selection step to the Quickstart and Terraform flows, adds a collapsible "Migrate an existing app registration to Secretless Auth" section with per-method tabs (Azure CLI, Terraform, Azure Portal), and updates the Terraform "Use an existing app registration" example to use secretless_auth_enabled.
  • Azure Resource Manager (ARM) guide — adds a Next steps link to the migration flow.
  • Azure advanced configuration guide — notes the federated-credential model alongside the client-secret architecture and links to the migration flow.

Merge instructions

Draft / work in progress. Not ready for review or merge yet — see Additional notes.

Merge readiness:

  • Ready for merge

Additional notes

Still to confirm before this is review-ready:

  • Site region restrictions (pending confirmation).

@jhgilbert
jhgilbert requested a review from a team as a code owner August 10, 2026 18:29
@jhgilbert jhgilbert added WORK IN PROGRESS No review needed, it's a wip ;) astro-reorg-auto-pr Needs manual conflict resolution after replatforming reorg labels Aug 10, 2026
@github-actions github-actions Bot added Images Images are added/removed with this PR Guide Content impacting a guide labels Aug 10, 2026
@buraizu buraizu added editorial review Waiting on a more in-depth review and removed WORK IN PROGRESS No review needed, it's a wip ;) labels Aug 10, 2026

@evazorro evazorro left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nothing blocking! A couple questions and small cosmetic things I noticed, but this is fine to merge as-is in my opinion.


{{< img src="/getting_started/integrations/azure/GSwAzure_secretlessMigration.png" alt="The General tab for an app registration, with a callout recommending Secretless Auth and a Set Up Secretless Auth button" style="width:100%;" >}}

In the {{< ui >}}Secretless Authentication Setup{{< /ui >}} dialog, select a setup method, then complete the steps for that method:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very minor, but it seems to me that this could be step 3 rather than body text following the procedure. Up to you, though!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah -- I think it's probably because it introduces the three tabs that follow.

Definitely out of scope for this PR, but the structure on this page seems like it has grown a little complicated: tabs within collapse sections, etc. Could be worth revisiting at some point to see whether it makes sense to break it up.


1. Add the federated credential resource shown in the dialog to the same configuration that manages your Datadog Azure integration, then apply it. Copy the `issuer` and `subject` values from the dialog.

{{< code-block lang="hcl" filename="" disable_copy="false" collapsible="false" >}}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code block looks like it might be misaligned with the step (or it could just be a quirk of the tab). Maybe 4 spaces instead of 3?

Image


## Next steps

{{< site-region region="us,us3,us5,eu,ap1,ap2,uk1" >}}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might be unavoidable with the site-region shortcode, but it looks like this divides the list:

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

astro-reorg-auto-pr Needs manual conflict resolution after replatforming reorg editorial review Waiting on a more in-depth review Guide Content impacting a guide Images Images are added/removed with this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants