Currently, the company I work for maintains several popular vscode extensions. However, after the VSCode Marketplace publisher token generation has been moved to Azure, we've dont have any way to access the organization which corresponds to the Marketplace publisher in order to generate new publishing tokens. We have no idea who has access to the Azure account within the company.
How can we gain access to the organization page?
Send an email to: Visual Studio Marketplace. (VSMarketplace#microsoft.com)
They can help you with the available options.
Related
Seeking input from anyone who has done this before.
We need to create additional organizations in GitHub that will be accessible to different groups of users so we moved to the Enterprise Cloud implementation. Our single Org will be moved into the Enterprise to absorb the seats into our Enterprise licenses.
We are using SAML SSO on our current org. I would like to setup a separate IdP definition for the Enterprise SSO configuration to start with and migrate the org users to the enterprise at a later time. Will this work as described?
I realize there may be some action innersource issues for private repos. But I think those just need to be changed to Internal.
If you have performed a similar migration, did you run into any unexpected issues? Do you have any tips to avoid any nasty hiccups?
The answer from their support groups is no, this will not work.
"configuring SSO at the Enterprise will overwrite SSO for all organizations under it."
When I'm working for external organization that owns Azure DevOps project, they usually create new AAD account for me in their organization.
Is it possible to use my Visual Studio (MSDN) Enterprise license with the account as well? (as well as with my own account, since I work on multiple projects)
Background:
In Azure DevOps, there are 5 users for free, additional licenses have to be bought unless the users have MSDN Subscription.
I have MSDN Subscription which shows as a user with Visual Studio Enterprise license in Azure DevOps.
However, when working for customers, I usually have to use different AAD account, which means they have to pay 5$/month even when I have the MSDN
From your description, you want to use an account that’s different from the one that your subscription is assigned to. You may go to http://my.visualstudio.com, click on Subscriptions, and then Add Alternate Account to add new account.
Some Azure DevOps users need to become Basic users instead of VS Enterprise users, because these users got another role in our organisation.
I removed the VS Enterprise subscription from these users in the MS partner portal (partner.microsoft.com). But Azure DevOps still sees the previously assigned VSE subscription for the users. And I cannot change the access level to Basic because Azure DevOps somehow detects the VSE subscription on the user.
How can I change the access level for the affected users?
Thanks for the input.
Currently, Azure Devops only validates the subscription when the user is added. So remove the user from the organization and then re-add them after removing the subscription should fix it.
Update to this since Eddie's answer is out of date
As of this date, Azure DevOps will automatically change access level based on Visual Studio Subscription (assuming the user is tied to the same email address in AzDO that their VS sub is tied to). You DO NOT have to remove the user from Azure DevOps and add them back in to get Visual Studio Subscription changes to appear in AzDo.
Scenario I observed 02/03/2021
Existing AzDO user had access level of: Visual Studio Professional subscription. User had license upgraded to Visual Studio Enterprise subscription on 02/02/2021. User logged out and back in on 02/03/2021 and access level updated correctly.
When using visual studio online, we want to ensure that contractors or developer working on project could only check-in and check-out using our given laptops.
Has anyone found a way to restrict access to code from a certain machines in Visual studio Online?
Can we somehow log who checked code out and from which machine at what time?
There is currently no way to restrict access to VSO by IP address. It is something we are considering. What you can do is to enable two-factor authentication in your Azure Active Directory tenant.
There's no way to currently log who has checked out code. The closest you could get would be to periodically query for the workspaces in the account if you are using TFVC. There's no way for you to track clones of Git repos.
Using Visual Studio Team Services you have to enable Alternative Credentials in order to be able to connect to TFS Git Repo. using Eclipse or any other Git Client,
My problem is i want to connect to TFS on-premises Git repo. using Eclipse but there is no way to enable Alternative Credentials, any way to enable Alternative Credentials to be able to do that ? or can i do it other way?
TFS15 now supports Personal Access Tokens and SSH access, so your question isit's not entirely off the mark. There are scenario's where connecting using NTLM or kerberos security is not possible, but as #edward-thomson pointed out, the alternate credential is still linked to a domain account and should not be handed out to 3rd parties.
Instead users will need to be added to Active Directory, or a trust relation (or Federation) needs to be in place so the user is able to join using it's own orgs AD account.
If you're using Git, you could opt to also store the repository on Visual Studio Team Services and push/pull between that and your own TFS server. That way you can give 3rd parties access using their MSA or AAD account, while keeping the main repository secured using AD accounts only. Given the fact that Git is able to transfer data and history with ease, that's not an entirely weird scenario. It fits with the whole Distributed nature of Git quite well.