Skip to main content

Visual Studio Online - Cannot add a new account (401, 403, TF400813)

By
In this post we will see what we need to do when we want to add a new user on our Visual Studio Online project, but we end up with errors like
  • 401
  • 403
  • TF400813
Let's start from the assumption that we are the administrator on VS Online. We added a user a few days ago on our project, with the same rights like other users. Even if we added the user, he is not able to access our project. It is well known that sometimes we need to wait a few hours until the rights and changes are propagated, but it never takes more than 12-24h.
In this moment we need to ask yourself what is different. There are times when the change propagation freeze and you need to remove and add the user again. We sad that this might be possible and let's remove the user and add him again to VS Online and to our project.
After removing the user we observed that we cannot find anymore the given account, even if it was a LIVE account. This was strange and odd. We remembered that a few days ago we had a similar issue (http://vunvulearadu.blogspot.ro/2015/12/visual-studio-online-administrators.html) because the integration between Azure AD and company AD.
We added the LIVE account to our AD as member. After this we added again the user to VS Online and project group.
New-MsolUser -UserPrincipalName user@contoso.com -DisplayName "User A B" -FirstName "User A" -LastName "B"
Set-MsolUser -UserPrincipalName user@company.com -UserType Member

Surprise, everything works as expected. The lesson learn is to double check the users in AD especially when under that subscription you have integration between on-premises AD and Azure AD.
Below you can find an MSND link where you can find the list of PowerShell comands that can be used in situations like this.
https://msdn.microsoft.com/en-us/library/azure/dn919674.aspx
Labels:

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Can User Technical Profile Influence AI Architecture Decisions?

By
In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more