Unanswered

Using User's Context to call Azure DevOps

(0) Share

Report

Posted on by sjin Microsoft Employee

What I'd like to do is that if a user enters a work item Id on a field, other detailed fields are populated from DevOps Work Item using Plug-ins.

I haven't seen any example that connecting with the external service (Azure DevOps). Is it possible to use a CRM user's context to AzureDevOps?

Impersonate a user (Microsoft Dataverse) - Power Apps | Microsoft Docs

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (6)

Answers (1)

EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report
Hi @sjin,

If I understand correctly if a user enters a work item ID in a Dataverse table/entity/form, you want some logic to populate other Dataverse fields from data in Azure DevOps? If so, then yes it's possible. I would recommend Power Automate rather than a plugin for a more flexible low code/no code solution.

You can use Azure DevOps connector and "Get Work Item Details" action

Use the When a row is added, modified or deleted from the Dataverse connector to trigger when the work item ID field is updated on the entity/table and "Update a row" action to update the record/row after retrieving the details from Azure DevOps.

The Dataverse connector will run under the user context automatically and you need to connect to Azure DevOps connector with a service account.

Hope this helps!

Was this reply helpful? Yes No
sjin Microsoft Employee on at

Like (0)

Report

Thanks for replying @EricRegnier . That's right.
I tried the Power Automate solution that you suggested before asking it on the forum. There was no option to use a service principal on Azure DevOps connector. Is it possible to use a signed-in user (Not admin) on Dynamics and retrieve the details?

Was this reply helpful? Yes No
Verified answer

EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Out-of-the-box not that I know of. But why do you specifically need that? Wouldn't a service account only used for that connector suffice and keep it simple. It would be more management to ensure the user also have the right Azure DevOps roles and whatnot, and cleanup the connector is a user leaves, etc.

Was this reply helpful? Yes No
sjin Microsoft Employee on at

Like (0)

Report

For security reason, we don't use Microsoft corporate account on a connector. For Common Data Service (Dataverse), we make the connection using Service Principal. That's why I was considering using Plug-in to use CRM user's context to AzureDevOps

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Is the Azure DevOps provisioned on the customer's tenant? If this is for production use, you'll need to have customer's account authenticate.

Ok that you're using a SPN for Dataverse integration which is good, but what about when configurating the tables and model-driven apps?

Was this reply helpful? Yes No
sjin Microsoft Employee on at

Like (0)

Report

No, it's for Azure DevOps (ADO). We have a separate repo to manage all work items. If a case/ticket on Dynamics is created, we'd like to link it to a relative ADO work items. I'll go with using a new service account to manage the connection between PowerAutomate and ADO only

Was this reply helpful? Yes No