I need to add a colleague to my development environment (specifically VisualStudioOnline - TFS) and the doc I've read about how to do this shows differently than what I see when I try.
I am the only user of Visual Studio 2012 in my small company. I am using Visual Studio Online for Source Control (as I understand it, this exposes Microsoft Visual Studio Team Foundation Service - Version 15.115.26417.0 as a "service" (i.e. this is the cloud...there is no on-premise TFS installed). Currently, I am using a LOCAL workspace (the default) and TFVC (not GIT).
I added my NewUserA to the Administrators group on the dev server. When click menu item Team to Connect to TFS, I am prompted to sign-in with my "Microsoft" account.
However, when I try to add NewUserA to my TFS, the dialog below seems unable to search for the existence of NewUserA:
It seems to want an "identity" of NewUserA (which suggests an email address too) so it sort of makes sense that this prompt does not look for locally added Windows users.
I am quite confused and would appreciate being helped thru this.
If your VSTS account isn't connected to Azure Active Directory and you're not synchronizing your on-premises AD to AAD, then of course it won't be able to find users from your on-prem domain. If that's the case, you can add users by email address and they'll be prompted to sign up for a Microsoft account (if they don't already have one) using that address. This is different than an organizational account, which is what you'd use if you were connected to Azure AD.
Related
I want to provide/restrict access to resources based on IP from my google cloud vm to prevent my dev team downloading/uploading the code to public drives.
Everything is working fine up to now.But I want to provide access to Visual studio online TFS with my outlook account.
I created visual studio online account for Version control.
URL: https://eschooltest.visualstudio.com
Region: Canada Central
I came to know vs online IPs are published every wednesday and downloaded from the below url and added these canada central Ips to Google Firewall system with allow access.
https://www.visualstudio.com/team-services/support/ip-addresses-used-hosted-build/
But still I am not able to access vs url.I pinged this url from command prompt and found the ip is 13.107.6.175 which is not present in the canada central IP list and also not present in the whole ip list of all regions.
Can someone help to achieve the requirement? OR please let me know if there is an elegant way of doing this.
if this is not possible with VS online, I am planning to set up TFS express in another VM to prevent leaking of my code to outside world though this is cumbersome.
EDIT:
1. Why this ip is not present in the Published xml?
VSTS does not offer any type of IP-based filter — so you can't do like in SQL Azure, in which you add and/or remove IPs that can access the service on Azure. About this area take a look at thie blog: Prevent users from accessing the VSTS out of the workplace
You should take a look at the official tutorial how to Manage conditional access to VSTS
Conditional access offers simple ways to help secure resources for
VSTS accounts backed by an Azure Active Directory (AAD) tenant.
Conditional access policies like multi-factor authentication can help
protect against the risk of compromised credentials and help keep your
organization's data safe. For example, in addition to requiring
credentials, you can have a policy that only devices connected to a
corporate network can gain access.
I was previously using Team Foundation services free account on the cloud with my Hotmail account. Now I am try to install TFS on a server computer. Everything worked fine. But then I noticed that I dont see the "Process" Menu option in my on Premise TFS account, while this shows up in the other account.
So, how can I enable "Process" menu option in my On Premise TFS web portal? So that I can configure the Work Item types and the process.
Below is my snapshot of my cloud account that does have the "Process" menu option.
While here is the image of On Premises account that has a very simple menu option.
The Process option menu only shows in Team Services (the cloud), there isn’t this option in On-Premises TFS web portal.
If you work in an on-premises TFS, and want to customize a process template,
you can download the zipped template file using the Process Template Manager. You'll need to use a version of Visual Studio that is at the same version level as TFS. You can install the latest version of Visual Studio Community for free.
Please see Upload or download a process template and Customize a process template for details.
To configure the Work Item types and the process please see Add or modify a work item type.
I have a question about Sharepoint Online debugging.
I've created a Sharepoint app with Visual 2015, destined to sharepoint-online and it's sharepoint hosted. Inside, I have a very simple workflow.
When I try to debug it, the following message appears:
Is it necessary to have an Azure account to debug a workflow? Are there any other options in workflow development?
If it helps, the deployment environment is Office 365.
It is necessary to have an Azure account to debug SharePoint Online/Office 365 workflows. This is because you can't access certain components that are used for debugging a local SharePoint workflow. Instead Microsoft created the Relay Service component of the Microsoft Azure Service Bus. (A secure component that they charge for hosting)
Before this component was released it does't appear debugging was possible. (See article below)
Debugging Workflows In SharePoint 2013 Online using Azure.
If you have an MSDN subscription or work for a Microsoft partner organization you should receive some free access to Azure.
Workflow debugging for SharePoint Online requires a Windows Azure Service Bus connection.
To enable remote debugging:
With a project selected in Solution Explorer, Right click on the Project menu ans select Properties.
Click the Debug tab.
Select the Use remote machine check box.
In the Use remote machine field, enter the name of the remote machine, using the format \\domain\machinename.
I'm having a pretty strange issue with Azure tools for VS 2013 (version 2.6). Whenever I try to sign in to my Azure subscription (e.g. from Server explorer or creating a new web role project) I get the following error:
Server Explorer
An error occurred during the sign in process: User 'foo#gmail.com' returned by service does not match user 'bar#outlook.com' in the request
OK
My subscription owned by 'bar#outlook.com' and I can perfectly fine sign in either to management portal in a browser (IE, Spartan and Chrome) - as well as in the Power Shell. Tried everything - cleaning up browser caches/cookies, resetting IE settings, playing with different IE security settings - nothign works.
Any help is appreciated - this issue drives me crazy.
P.S. I'm on Windows 10...
I had the same problem. Imported the certificate manually and everything worked ok: https://social.technet.microsoft.com/Forums/en-US/9cdafeb4-f459-436d-b2b8-9bc5c01f0df1/azure-tools-for-vs-cant-sign-in-to-subscription?forum=windowsazuredevelopment
I had this issue, to resolve it I:
Added 'foo#gmail.com' as an alias in my 'bar#outlook.com' Microsoft account, via account.live.com
Made the 'foo#gmail.com' email address the primary alias for my Microsoft account
I could then log in successfully in to Azure by pressing the Connect to Microsoft Azure button in the toolbar of the Server Explorer in Visual Studio 2013 and see all of my websites under the App Service node.
(When I'd used the certificate method described in the other post and Microsoft documentation I'd been able to see all my sql databases etc. but not the websites.)
Once I'd done all that I then switched my primary alias back to 'bar#outlook.com' and server explorer carried on working.
NB: If you're experimenting with this beware that there is a limit on how many times you can switch your primary.. as I have just discovered.. and now my primary is stuck on the wrong email address for a week.
NB2: If your connecting in order to be able to remote debug the website, then this can still be done by going to Visual Studio>Main Menu>Debug>Attach To Process, and then enter the URL of the site (without the http bit, e.g. mysite.azurewebsites.net) as the Qualifier and then attach to the w3wp.exe process.
I am having the exact same issue. It seems that the Azure sign-in in Visual Studio is redirecting to our organizational Single Sign-On instead of the Microsoft one. I have managed to work around this problem by using a Microsoft account that is not tied to my organization:
Create new Microsoft account or use an existing account not associated with your organization
In https://manage.windowsazure.com select Subscriptions/Manage Administrators
Choose Add+ and add the new Microsoft account as administrator to your subscription
Log on to Azure using the new account from Visual Studio
/Morten
I changed my Microsoft account's email address and had this problem. Adding an alias did not help.
The problem is to do with the Azure Active Directory Library for DotNet. For whatever dumb reason, they throw an exception when Azure returns an ID different than the one requested (if the server isn't crying about it, why make up an error and make the client deal with it?).
Since Azures's support was no help, I had to build a custom copy of the ADAL with that moronic exception removed and an assembly version matching the one used in VS2013 (2.11). Also importantly, disable strong name verification for the custom assembly.
We're using Azure to maintain our development and QA servers.
One of the needs we have now, is to provide our QA members access to update web.config file on the server, which can be achieved via Visual Studio Server's Explorer (with the right configuration).
The problem is that you need a user with a subscription as a co-administrator within Azure (at least as far as I managed to understand), but obviously we'd like to allow our QA members only to maintain the files, with limited access via Visual Studio.
Is there any way to do it?
Following Brendan advice, I've granted the QA members FTP access. This should do the job for now, until Microsoft will come up with something better :)
Thanks Brendan!