Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding redirect URI to ADO #6843

Merged
merged 5 commits into from
Jan 29, 2025
Merged

Adding redirect URI to ADO #6843

merged 5 commits into from
Jan 29, 2025

Conversation

matthewshaver
Copy link
Contributor

@matthewshaver matthewshaver commented Jan 28, 2025

What are you changing in this pull request and why?

Adds instructions for redirect URI

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:

@matthewshaver matthewshaver requested a review from a team as a code owner January 28, 2025 20:59
Copy link

vercel bot commented Jan 28, 2025

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 29, 2025 4:08pm

@github-actions github-actions bot added content Improvements or additions to content Docs team Authored by the Docs team @dbt Labs size: x-small This change will take under 3 hours to fix. labels Jan 28, 2025
6. Set **Redirect URI (optional)** to **Web**. Copy the value from dbt Cloud to the next field:
1. In dbt Cloud, navigate to **Account Settings** -> **Integrations**.
2. Click the **edit icon** next to **Azure DevOps**.
3. Copy the first **Redirect URIs** value to the field in Azure (not the value that ends with azure_active_directory_service_user). It will look like `https://<YOUR_ACCESS_URL>/complete/azure_active_directory`.
Copy link
Contributor

Choose a reason for hiding this comment

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

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

Copy link
Collaborator

@runleonarun runleonarun left a comment

Choose a reason for hiding this comment

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

I was just a little confused but figured it out and suggest these changes

6. Set **Redirect URI (optional)** to **Web**. Copy and paste the Redirect URI from dbt Cloud into the next field. To find the Redirect URI in dbt Cloud:
1. In dbt Cloud, navigate to **Account Settings** -> **Integrations**.
2. Click the **edit icon** next to **Azure DevOps**.
3. Copy the first **Redirect URIs** value to the field in Azure (not the value that ends with azure_active_directory_service_user). It will look like `https://<YOUR_ACCESS_URL>/complete/azure_active_directory`.
Copy link
Contributor

Choose a reason for hiding this comment

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

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

@matthewshaver matthewshaver enabled auto-merge (squash) January 29, 2025 16:03
@matthewshaver matthewshaver merged commit 05c91b2 into current Jan 29, 2025
8 checks passed
@matthewshaver matthewshaver deleted the ado-update branch January 29, 2025 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content Docs team Authored by the Docs team @dbt Labs size: x-small This change will take under 3 hours to fix.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants