You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, only host names can be added to the list of Sites assigned to a container. For some sites, it is highly useful to open certain paths in certain containers, for example:
dev.azure.com/ClientA -> Container A
dev.azure.com/ClientB -> Container B
Now I cannot configure this, and if I configure dev.azure.com to be always be opened in Container A, I cannot reach dev.azure.com/ClientB since it must be accessed by an account which is logged in in Container B. If I open dev.azure.com/ClientB in Container B, the tab closes and the and the site is opened in Container A, which is not allowed to access that Azure DevOps account.
The text was updated successfully, but these errors were encountered:
Currently, only host names can be added to the list of Sites assigned to a container. For some sites, it is highly useful to open certain paths in certain containers, for example:
Now I cannot configure this, and if I configure dev.azure.com to be always be opened in Container A, I cannot reach dev.azure.com/ClientB since it must be accessed by an account which is logged in in Container B. If I open dev.azure.com/ClientB in Container B, the tab closes and the and the site is opened in Container A, which is not allowed to access that Azure DevOps account.
The text was updated successfully, but these errors were encountered: