search

microsoft / DevHomeAzureExtension

Dev Home Azure Extension
MIT License
68 stars 15 forks source link

Support Azure DevOps Server #45

Open mikebattista opened 7 months ago

mikebattista commented 7 months ago

Suggested new feature or improvement

Make sure we parse Azure DevOps Server URIs properly and all functionality works as expected.

Scenario

Users connecting to their on-premise deployments of Azure DevOps Server.

Additional details

No response

soroshsabz commented 7 months ago

This is very important feature

Reza-Noei commented 7 months ago

Please add this feature.

MostafaFarajbakhsh commented 7 months ago

Would you mind adding this feature.🙏

soroshsabz commented 4 months ago

How to add AzureDevOps Server account to Dev Home?

soroshsabz commented 4 months ago

I do not see AD User input for Azure Account

image

soroshsabz commented 4 months ago

@dkbennett @krschau

I think this issue is not complement yet, and must be reopen

krschau commented 4 months ago

@soroshsabz Please note that this issue is labeled "Fix-Committed", which if you hover over it says that the fix has been checked in, but may take 3-4 weeks before it is in a release. The issue is also in milestone 0.7, meaning the feature is coming out in 0.7, our release next month.

mikebattista commented 3 months ago

@dkbennett

We did some work in the latest release to support entering on-prem ADO server URIs when setting up widgets, etc. but need some validation in the wild.

If you're interested in connecting to ADO Server deployments via Dev Home, please try with the latest version of the app and let us know your experience.

soroshsabz commented 2 months ago

@mikebattista I use 0.1201.442.0 and 0.700.442.0 for Dev Home Azure Extension and I do not find anything related to ADO Server

krschau commented 2 months ago

@dkbennett FYI

mikebattista commented 2 months ago

The test flow would be to connect your Microsoft or Work account that you use in ADO Server to Dev Home in Dev Home Settings -> Accounts -> Add -> Azure then set up an ADO widget on the Dev Home dashboard that points to a URL in your ADO Server.

soroshsabz commented 2 months ago

As you can see in below, I click on Work or school account

image

But this is open Microsoft SSO, instead of open a dialog to enter my AzureDevOps Server local address

image

I try cannot access link and get below error (Of course, this was pointless from the beginning(

image

soroshsabz commented 2 months ago

@mikebattista We need one page to enter Azure DevOps Server local address, and then add credential, and gain access to our account

mikebattista commented 2 months ago

You need to connect your account first. ADO Server flow and auth is different than GitHub Enterprise Server flow.

If you used an external email address when initially connecting to ADO, that should be a "Microsoft account" under the hood (not a "Work or school account"). If you used an organizational account with its own domain, that would be a "Work or school account".

actionthomas commented 2 months ago

Azure Devops Server is not tied in any way to an online account. Authentication is based on the local Active Directory domain. In the past, when using a tool connecting to ADS/TFS, we had windows like this: image Eventually followed by a credentials prompt.

This was the place we used to enter the Azure Devops Server collection URL. I think that's the part missing here.

BryanAldrich commented 2 months ago

Just wanted to add that our on premises DevOps server is attached to an AD domain that isn't attached to our laptop. We have to authenticate everytime. There is zero trust between the two domains.

mikebattista commented 2 months ago

Thanks. For GitHub Enterprise Server, we have a flow where you enter the server and then enter a PAT. Would that flow work in your ADO Server scenarios?

BryanAldrich commented 2 months ago

Yes, developers could make a PAT and authenticate that way. Since Dev Home doesn't do any sql access, (which for us is.. complicated..) just a plain PAT is simplest.