Rearranging ADO page

[matthewshaver]

What are you changing in this pull request and why?

This moves around some sections and brings the full Service User instructions back. This is a bandaid for some clients between worlds and utilizes two H1 headers. I know this is a little outside our style requirements, but this would be helpful.

Splits the ADO setup into two docs - one for service principal one for service user
Updates the intro page to link to the appropriate files

There is a banner up top that is new language in need of review

https://www.notion.so/dbtlabs/Azure-DevOps-Service-Principal-18abb38ebda7808f96bcf4a4bc9a4944?pvs=4

Checklist

• I have reviewed the Content style guide so my content adheres to these guidelines.
• The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
• I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
• The content in this PR requires a dbt release note, so I added one to the release notes page.

---

🚀 Deployment available! Here are the direct links to the updated files:

• https://docs-getdbt-com-git-ado-updates-dbt-labs.vercel.app/docs/cloud/git/connect-azure-devops
• https://docs-getdbt-com-git-ado-updates-dbt-labs.vercel.app/docs/cloud/git/setup-azure-service-principal
• https://docs-getdbt-com-git-ado-updates-dbt-labs.vercel.app/docs/cloud/git/setup-azure-service-user

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs-getdbt-com	✅ Ready (Inspect)	Visit Preview	Jan 28, 2025 6:13pm

[github-actions]

⚠️ [vale] _{reported by reviewdog 🐶}
[custom.Typos] Oops there's a typo -- did you really mean 'user_impersonation'?

[runleonarun]

Approved with some wording suggestions!

[runleonarun]

Suggested change

	To use dbt Cloud's native integration with Azure DevOps, an account admin needs to set up an Microsoft Entra ID app as a service principal. We recommend setting up a separate [Entra ID application than used for SSO](/docs/cloud/manage-access/set-up-sso-microsoft-entra-id).
	To use dbt Cloud's native integration with Azure DevOps, an account admin needs to set up a Microsoft Entra ID app as a service principal. We recommend setting up a separate [Entra ID application than used for SSO](/docs/cloud/manage-access/set-up-sso-microsoft-entra-id).

[sidpatel13]

Two changes I'm requesting:

1. I want us to move service user to a separate page rather than having all 3 sections on adding service principal for the first time, migrating to service principal and service user overview on the same page to avoid any confusion.
2. The migrating to service principal might still be incorrect. We don't want the user to add in the app credentials again, rather we want to tell them to use the same app for service principal which they used for service user to begin with. They need to go to org settings > users and add their service user app registration as a service principal. The adding the user to the ADO org settings might be missing as well which we need to add.

To avoid the back and forth and so we can ship this early next week, I've scheduled a pairing session for us. Let me know if there's a better time for you if that doesn't work. Thanks!

[sidpatel13]

This URL for service user doesn't work. I think it needs to be #connect-a-service-user

[runleonarun]

Thanks for proactively setting time up with @matthewshaver on Monday, @sidpatel13!

[sidpatel13]

typo: Available

[sidpatel13]

Can we update this line and include the other section that is relevant here as well which is to connect azure devops. Following the remaining instructions is misleading since it will also include adding the app details to dbt cloud which we don't want the migration flow to include