I am looking to connect to azure sql server in Visual studio code using one of the Active Directory connection modes. However seems only sql authentication is supported as of now in visual studio code. Any help here is appreciated.
Tried checking in visual studio code documentation but didn't find any mention of active directory authentication
Please consider using Azure Data Studio, which is derived from VS Code for use with SQL Azure and other Azure Data services. It supports Azure Active Directory authentication (which is a bit different than traditional integrated authentication against a local AD. Given that SQL Azure isn't domain joined to your local domain, you would not be able to use it to authenticate anyways.
Here's the release notes where they mention AAD auth supportRelease Notes.
Related
In our solution we are interacting with SAP using the "Classic" API of the SAP RFC SDK.
We have hosted the application in Azure Services, hence not possible to place the librfc32.dll in the required path of C drive.
We have added the librfc32.dll in the solution and marked it Copy Always to the folder.
While we publish the solution locally and deploy using FTP in Azure Services, it works fine.
However when deployed using ADO pipeline, it gives the below error.
We have checked both published and ADO generated artifact and in both places the librfc32.dll is present fine.
Cannot call classic RFC API. See help for details. Please put a recent 64-bit version of librfc32.dll in your System32 folder (typically C:\Windows\System32). See SAP note 413708. Please make sure you have installed Visual C++ 2005 SP1 ATL Security Update (x64). An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
Any suggestion?
I want to implement Team Foundation Server (now known as Azure DevOps Server) for source control and issue tracking. I have only used the on-premises solution previously. For this particular use case, it would be beneficial to have it hosted in the cloud.
I have deployed a VSTS/Azure DevOps Services cloud solution (as opposed to an on-premises TFS/Azure DevOps Server solution), and it seems to have all of the functionality I am used to with the web portal, except there seems to be no direct integration/plugin for Visual Studio.
I can connect Team Explorer to it and query the work items for a basic listing (as shown in the screenshot below) - but if I double click a work item, or if I click New Work Item, it opens in the web browser, not within Visual Studio.
Is this expected behaviour for VSTS/DevOps Services? Do I need an on-premises installation just to get Visual Studio integration or am I missing something? I would like to use their cloud solution as it has a lot of benefits for this particular use-case.
Which opens this:
Instead of this (below screenshot taken from the web):
Any help is much appreciated! I am hoping to get something up and running ASAP, and would rather not have to install & configure a full on-premises solution in the cloud myself. Letting Microsoft handle it is perfect.
It seems odd that there's no Visual Studio support/integration. I have tried on 2 different machines. I have connected one machine which is running Visual Studio 2017 Professional and the other has VS 2019 Professional. Both open and create work items in the web browser instead of within VS. But VSTS/DevOps Services does seem to have all of the other features of TFS/DevOps Server, as far as I can see.
The web portal is great for other stakeholders, but as a developer I like working directly within Visual Studio. In an on-premises installation you get both. Is there any way to do this on a cloud installation?
We need set the Work Items experience in Visual Studio, then we can create new work item in the visual studio.
Steps:
Tools->work items->General->change the option Landing page.
Result:
How can I add an external TFS Connection to TFS 2017 to allow it to connect to TFS 2013?
I navigated to http://tfsserver:8080/tfs/collection/team_project_name/_admin/_services?_a=resources and clicked New Service Endpoint. I selected External TFS
When I go to verify the connection after entering all the relevant information, I get the below error.
Failed to query service endpoint api: http://tfsserver:8080/tfs/collection/_apis/projects. Error Message: The remote server returned an error: (401) Unauthorized..
Here is a screenshot of the error.
The odd thing is that if I make a GET request to http://tfsserver:8080/tfs/collection/_apis/projects without any authentication I get a 200 OK response back with project information.
I have configured basic authentication per the tfs cli guide. How can I verify that basic authentication is configured correctly? When I try to login with tfx, I get the following screen.
I have the following extensions installed on the TFS 2017 instance.
Package Management
Release Management Utility tasks
TFS artifacts for Release Management
I am using Microsoft Visual Studio Team Foundation Server Version 15.105.25910.0
According to the screenshot, you are using TFS artifacts for Release Management extension to connect to another TFS instance.
Make sure the things below:
Make sure the collection URL you enter is correct. In your screenshot, the URL you enter is ended with "_home".
Make sure Basic Auth is enabled on TFS server.
Seems you are using the extension TFS artifacts for Release Management which provides a service endpoint to connect to an external TFS or VS Team Services Collection.
After test with TFS2013, I could reproduce your issue and got the same error information. The solution please see below:
Since you are connecting to TFS2013, it works with basic
authentication only. You’ll need to enable basic authentication
support for the TFS Server which handling TFS2013.
Also please make sure the username to connect to the external TFS
collection are with Domain in front of. Then will get a green
verfifed status.
I am not able to login to my azure account from Visual Studio Professional 2012. I am getting an error shown below
However I am able to login to my Azure account using browser.
I have performed below steps
1) Opened Server Explorer in Visual Studio
2) Clicked on Microsoft Azure Subscription icon
3) Sign in Dialog Box opens up asking for my email, which I provided and clicked continue
4) Selected Microsoft Personal Account from the option provided
5) Entered Password clicked submit
6) Error dialog box opens up as shown earlier.
I feel that it is related to management certificate as I am also not able to run certain commands like Get-AzureDeployment from Azure PowerShell, whereas Get-AzureSubscription works fine.
I have already saved publishsettings file from Azure and there are certificates installed in Personal section in Certificate manager.
I was able to resolve the problem. As I could see that Visual Studio and Power shell both were failing. Visual Studio was not able to connect to Azure and Power shell scripts where I was trying to add Azure Account failed. By doing a bit more searching and reading few article, I came to know that Visual Studio as well as Power shell scripts apart from using your credentials for azure also use management certificate to communicate with azure. A network tool used in our organization was causing issue in this https communication. Just got it enabled from IT team and I am done.
I want to run PS scripts in C# exactly along the lines of Sample
This works on a Cloud Service (Web Role), on a standard server (with execution policy disabled), but not in a Azure Web Site.
Anyone know why this is so?
I don't know of any official documentation on the issue but there are multiple answers on the related forums where Microsoft employees talk about the limitations of not being able/allowed to launch external processes in Windows Azure Web Sites. See
PHP - Warning: exec(): Unable to fork
PDF Generator failing on Azure Website but not development machine
Recommended HTML to PDF Generator that works on Azure Website Reserved mode with Full Trust
You are probably trying to do that with your powershell script.
You could verify if that is in fact your issue by catching and looking at the exception(s) which should relate to security policies/permissions.