Skip to content

Commit 68f0a4e

Browse files
Merge pull request #9097 from MicrosoftDocs/main
Auto Publish – main to live - 2026-04-03 13:00 UTC
2 parents 2cfc1af + c6b9b32 commit 68f0a4e

11 files changed

Lines changed: 316 additions & 349 deletions

File tree

docs/boards/backlogs/manage-bugs.md

Lines changed: 90 additions & 111 deletions
Large diffs are not rendered by default.

docs/boards/includes/basic-process-bug-note.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,12 @@ ms.service: azure-devops-boards
33
ms.author: chcomley
44
author: chcomley
55
ms.topic: include
6-
ms.date: 07/29/2025
6+
ms.date: 04/02/2026
77
---
88

99
::: moniker range="<=azure-devops"
1010

1111
> [!NOTE]
12-
> Bug work item types aren't available with the Basic process. The Basic process tracks bugs as Issues and is available when you create a new project from Azure DevOps Services or Azure DevOps Server 2020 or later versions.
12+
> The Basic process doesn't include a Bug work item type. Instead, it tracks bugs as Issues.
1313
1414
::: moniker-end

docs/integrate/get-started/authentication/entra-oauth.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,23 @@
11
---
2-
title: Building Azure DevOps integrations with Microsoft Entra OAuth apps
3-
description: Use Microsoft Entra authentication to integrate with Azure DevOps Services.
4-
ms.assetid: 19285121-1805-4421-B7C4-63784C9A7CFA
2+
title: Build Azure DevOps integrations with Microsoft Entra OAuth apps
3+
description: "Microsoft Entra OAuth apps: Discover how to build secure Azure DevOps integrations using delegated authentication and enhance your development process."
54
ms.subservice: azure-devops-security
6-
ms.custom: pat-reduction
5+
ms.custom: pat-reduction, UpdateFrequency3
76
ms.topic: overview
87
monikerRange: 'azure-devops'
98
ms.author: chcomley
9+
ms.reviewer: chcomley
1010
author: chcomley
11-
ms.date: 01/08/2025
11+
ms.date: 04/02/2026
1212
---
1313

1414
# Build Azure DevOps integrations with Microsoft Entra OAuth apps
1515

1616
[!INCLUDE [version-eq-azure-devops](../../../includes/version-eq-azure-devops.md)]
1717

18-
The Microsoft identity platform offers many ways to authenticate users via [the OAuth 2.0 protocol](/entra/identity-platform/v2-protocols). In these docs, we use OAuth tokens to colloquially refer to [on-behalf-of user flows](/entra/identity-platform/v2-oauth2-on-behalf-of-flow), also known as [delegated flows](/entra/identity-platform/delegated-access-primer), for apps that request tokens to perform actions for their users.
18+
The Microsoft identity platform offers many ways to authenticate users via [the OAuth 2.0 protocol](/entra/identity-platform/v2-protocols). In this article, *OAuth tokens* refers to [on-behalf-of user flows](/entra/identity-platform/v2-oauth2-on-behalf-of-flow), also known as [delegated flows](/entra/identity-platform/delegated-access-primer), where apps request tokens to perform actions for their users.
1919

20-
This differs from apps that perform actions on-behalf-of themselves. For that, you would use [service principals and managed identities](service-principal-managed-identity.md).
20+
This approach differs from apps that perform actions on-behalf-of themselves. For that approach, use [service principals and managed identities](service-principal-managed-identity.md).
2121

2222
## Resources for developers
2323

@@ -34,13 +34,13 @@ This differs from apps that perform actions on-behalf-of themselves. For that, y
3434
* [Add an enterprise application](/entra/identity/enterprise-apps/add-application-portal)
3535
* [Explore the consent experience for applications in Microsoft Entra ID](/entra/identity-platform/application-consent-experience)
3636

37-
## Tips for building & migrating
37+
## Tips for building and migrating
3838

39-
* Microsoft Entra apps don't natively support Microsoft account (MSA) users for the Azure DevOps resource. If you're building an app that must cater to MSA users or support both Microsoft Entra and MSA users, [Azure DevOps OAuth apps](azure-devops-oauth.md) remain your best option. We're currently working on native support for MSA users through Microsoft Entra OAuth.
39+
* Microsoft Entra apps don't natively support Microsoft account (MSA) users for the Azure DevOps resource. If you're building an app that must cater to MSA users or support both Microsoft Entra and MSA users, [Azure DevOps OAuth apps](azure-devops-oauth.md) remain your best option. Microsoft is currently working on native support for MSA users through Microsoft Entra OAuth.
4040
* Azure DevOps' resource identifier: `499b84ac-1321-427f-aa17-267ca6975798`
4141
* Azure DevOps' resource URI: `https://app.vssps.visualstudio.com`
4242
* Use the `.default` scope when requesting a token with all scopes that the app is permissioned for.
43-
* In a previous Azure DevOps OAuth app, you might have use Azure DevOps user identifiers that don't exist in Microsoft Entra. When migrating to Microsoft Entra, use the [ReadIdentities API](/rest/api/azure/devops/ims/identities/read-identities) to resolve and match the different identities used by each identity provider.
43+
* In a previous Azure DevOps OAuth app, you might have used Azure DevOps user identifiers that don't exist in Microsoft Entra. When migrating to Microsoft Entra, use the [ReadIdentities API](/rest/api/azure/devops/ims/identities/read-identities) to resolve and match the different identities used by each identity provider.
4444

4545
## Related content
4646

docs/organizations/accounts/resolve-orphaned-organization.md

Lines changed: 30 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,89 +1,90 @@
11
---
22
title: Assign an owner to an orphaned organization
33
titleSuffix: Azure DevOps Services
4-
description: Learn how to assign a new owner to an organization when the current owner's inactive.
4+
description: Assign an owner to an orphaned organization in Azure DevOps. Learn step-by-step how to restore access and resolve inactive administrator issues. Start now.
55
ms.subservice: azure-devops-organizations
6-
ms.assetid: b81adafa-adac-4e80-baa6-140fb58fbeff
76
ms.topic: how-to
87
ms.author: chcomley
8+
ms.reviewer: chcomley
99
author: chcomley
1010
ai-usage: ai-assisted
11-
ms.date: 03/02/2026
11+
ms.date: 04/02/2026
1212
monikerRange: 'azure-devops'
13-
ms.custom: copilot-scenario-highlight
13+
ms.custom: copilot-scenario-highlight, UpdateFrequency3
1414
---
1515

1616
# Assign an owner to an orphaned organization
1717

1818
[!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
1919

20-
When the organization owner and all project collection administrators are inactive, the organization is considered orphaned. An orphaned organization doesn't have an administrator, so there's no way to transfer administrator rights to another user.
21-
22-
[!INCLUDE [ai-assistance-mcp-server-tip](../../includes/ai-assistance-mcp-server-tip.md)]
23-
24-
25-
But, organizations connected to Microsoft Entra ID can transfer ownership to an active user.
20+
An organization becomes *orphaned* when the organization owner and all Project Collection Administrators are inactive. Because no active administrator exists, you can't transfer ownership through the normal process. However, if the organization is connected to Microsoft Entra ID, an Azure DevOps Administrator in Microsoft Entra ID can claim ownership and assign it to an active user.
2621

2722
> [!NOTE]
28-
> If your organization isn't considered orphaned and you want to change the owner, see [Change organization owner](change-organization-ownership.md).
23+
> If your organization isn't orphaned and you want to change the owner, see [Change organization owner](change-organization-ownership.md).
24+
25+
[!INCLUDE [ai-assistance-mcp-server-tip](../../includes/ai-assistance-mcp-server-tip.md)]
2926

3027
## Prerequisites
3128

3229
| Category | Requirements |
3330
|--------------|-------------|
3431
|**Permissions**|[Azure DevOps Administrator in Microsoft Entra ID](../security/look-up-azure-devops-administrator.md). If using [Privileged Identity Management](/azure/active-directory/privileged-identity-management/pim-configure?msclkid=303229fdc6c111ecaf0f666b2dd9cd6f), the Azure DevOps Administrator should be of type [Active](/azure/active-directory/privileged-identity-management/pim-how-to-add-role-to-user?msclkid=5cdc55f5c6c011eca737e344cbe17b42).|
3532

36-
> [!NOTE]
37-
> Claim ownership of organizations only when the current owner and all members of the Project Collection Administrators group are inactive in the backing Microsoft Entra ID. Azure DevOps and Microsoft Entra ID define inactive user accounts the same way. For more information, see [What are inactive user accounts?](/azure/active-directory/reports-monitoring/howto-manage-inactive-user-accounts).
33+
> [!IMPORTANT]
34+
> Only claim ownership when the current owner *and* all members of the Project Collection Administrators group are inactive in Microsoft Entra ID. For the definition of inactive, see [What are inactive user accounts?](/azure/active-directory/reports-monitoring/howto-manage-inactive-user-accounts).
3835
3936
### Find your Azure DevOps Administrator
4037

41-
The Azure DevOps Administrator can [change the Azure DevOps owner](change-organization-ownership.md) to claim ownership of the target Azure DevOps organization.
38+
If you don't know who has the Azure DevOps Administrator role in your Microsoft Entra tenant, see [Look up the Azure DevOps Administrator](../security/look-up-azure-devops-administrator.md).
4239

4340
> [!NOTE]
44-
> Any changes to role membership might take up to an hour to propagate to Azure DevOps.
41+
> Changes to role membership might take up to an hour to propagate to Azure DevOps.
4542
4643
## When your Azure DevOps Administrator is a member of the target organization
4744

48-
When your Azure DevOps Administrator in Microsoft Entra ID *is* a member of the target Azure DevOps organization, do the following steps.
45+
Complete the following steps when the Azure DevOps Administrator *is* a member of the target organization.
4946

50-
1. As the Azure DevOps Administrator, sign in to your organization (```https://dev.azure.com/{yourorganization}```).
47+
1. Sign in to your organization (`https://dev.azure.com/{yourorganization}`) by using the Azure DevOps Administrator account.
5148

52-
2. Select **Organization settings** > **Overview**.
49+
1. Select **Organization settings** > **Overview**.
5350

54-
3. In the warning message, select **Change owner**.
51+
1. In the warning message, select **Change owner**.
5552

5653
![Screenshot of warning, PCA and Owner inactive in Microsoft Entra ID.](media/change-organization-ownership/warning-message-change-owner.png)
5754

58-
4. Select a user from the dropdown menu, or search for a user by entering the user's name, provide a short justification, and then select **Change**.
55+
1. Select a user from the dropdown menu or search by name.
56+
57+
1. Enter a short justification, and then select **Change**.
5958

6059
![Screenshot of button highlighted by red box, Change owner.](media/change-organization-ownership/change-organization-owner.png)
6160

62-
A notification of the ownership transfer with your provided justification gets sent to all Azure DevOps Administrators in your Microsoft Entra ID.
61+
The ownership transfer notification with your justification is sent to all Azure DevOps Administrators in your Microsoft Entra tenant.
6362

6463
## When your Azure DevOps Administrator isn't a member of the target organization
6564

66-
When your Azure DevOps Administrator in Microsoft Entra ID *isn't* a member of the target Azure DevOps organization, do the following steps:
65+
Complete the following steps when the Azure DevOps Administrator *isn't* a member of the target organization.
6766

68-
1. Sign in to your organization (```https://dev.azure.com/{yourorganization}```) using the credentials granted to the Azure DevOps Administrator role in Microsoft Entra ID.
67+
1. Sign in to your organization (`https://dev.azure.com/{yourorganization}`) by using the Azure DevOps Administrator account.
6968

70-
An error page appears where you can claim ownership.
69+
An error page appears because the account isn't a member of the organization.
7170

7271
![Screenshot of 401 message: Microsoft Entra Administrator not member of organization.](media/change-organization-ownership/error-message-administrator-not-member-of-organization.png)
7372

74-
2. Select **Claim Ownership**, provide a short justification, and then select **Claim Ownership** once again.
75-
76-
A notification of the ownership transfer with your provided justification gets sent to all Azure DevOps Administrators in your Microsoft Entra ID.
73+
1. Select **Claim Ownership**.
74+
75+
1. Enter a short justification, and then select **Claim Ownership** again.
7776

7877
![Screenshot showing empty box, where you enter justification and claim ownership of the organization.](media/change-organization-ownership/claim-ownership.png)
7978

80-
You're redirected to the organization overview page. To transfer ownership to another user, see [Change organization owner](change-organization-ownership.md).
79+
A notification of the ownership transfer with your justification is sent to all Azure DevOps Administrators in your Microsoft Entra tenant. You're redirected to the organization overview page.
80+
81+
1. To transfer ownership to another user, see [Change organization owner](change-organization-ownership.md).
8182

8283
<a id="use-ai-assistance"></a>
8384

8485
## Use AI to resolve orphaned organizations
8586

86-
If you have the [Azure DevOps MCP Server](../../mcp-server/mcp-server-overview.md) configured, you can use AI assistants to investigate orphaned organizations and gather ownership details using natural language prompts. The MCP Server provides your AI assistant with secure access to your Azure DevOps data, allowing you to check organization ownership, list administrators, and verify Microsoft Entra connections without navigating through the web interface.
87+
If you have the [Azure DevOps MCP Server](../../mcp-server/mcp-server-overview.md) configured, you can use AI assistants to investigate orphaned organizations and gather ownership details using natural language prompts. The MCP Server provides your AI assistant with secure access to your Azure DevOps data, so you can check organization ownership, list administrators, and verify Microsoft Entra connections without navigating through the web interface.
8788

8889
### Example prompts for resolving orphaned organizations
8990

0 commit comments

Comments
 (0)