I can import and export Notebooks using the Workspace API. Is there a way to link a Notebook to a Git repository using an API (not the Portal)?
unfortunately, there is no Workspacece API to link Azure Databricks Notebook to Git.
You need to use Azure portal to Link a notebook to GitHub.
Note: The Workspace API allows you to list, import, export, and delete notebooks and folders.
Reference: Azure Databricks - GitHub version control
I would suggest you to provide feedback on the same:
https://databricks.com/feedback
All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.
Related
I am following a series of instructions to deploy a mobile backend using Azure Mobile Services.
As part of that workflow I get to download a personalized backend app which downloads as Visual studio solution.
It builds fine and the next step is to publish it to Azure.
Instead of seeing the choice below (Microsoft Azure App Service) I am seeing 2 different choices
Microsoft Azure Web Apps, or
Microsoft Azure API Apps (Preview).
So, I chose the closest option (Web Apps) provided and it logs me into Azure and in a box which reports existing web apps I see none.
Yet I've deployed a mobile app in the Azure portal earlier.
In some of what I've been reading online it mentions a Publisher profile. I am just a bit stumped by not getting the "Microsoft Azure App Service" choice when I go to publish my backend to the cloud.
Here is the tutorial/guide which I am following (January 2016).
Perhaps the VS/Azure integration has changed since then or maybe I've more configuration steps missing.
Azure .NET mobile backend using Azure Mobile Services
Any guidance would be hugely welcome.
At this stage I am stuck as far as what I need to do to get my mobile backend published to Azure.
You have got an older version of the Azure SDK installed. The latest version of the Azure SDK provides the Azure App Service publish dialog.
I think I've solved this for now.
I was able to download a publish profile from the Azure Console which I could import within the "publish" dialog in VS2015.
I now have the mobile app up and running in Azure.
I've been at this for hours, can't seem to link my Team Services project with Azure. The screenshot below show that no projects are pulling up! I've tried using Azure Portal to link my account, setting up an endpoint on Team Services, etc. Any ideas?
Your issue is similar to this. There must be a git repository in a team project of your VSTS.
Visual Studio Online is available in Azure for creating Team Projects on cloud. Now what i have a doubt is if we can restrict the access of VSO from just corporate network or not? If yes how can we achieve that? Can anyone provide links or steps to configure it? Can Azure Active Directory help in this case?
For eg: There is XYZ Company that wants its developers to work with VSO only while they are on premise of the office. When they go home or outside corporate's network he/she must not be able to access or make changes in VSO.
Any help will be appreciated.!!
I think you can do it via using Azure Active Directory.
As we know that Azure AD can be integrated with an existing Windows Server Active Directory, giving organizations the ability to leverage their existing on-premises identity. Please check:
http://blogs.technet.com/b/ad/archive/2014/08/04/connecting-ad-and-azure-ad-only-4-clicks-with-azure-ad-connect.aspx
If the Visual Studio Online account is connected to an active directory, only users in that directory can get access to your account.
Please check the following two links for the details:
https://www.visualstudio.com/get-started/setup/manage-organization-access-for-your-account-vs
http://nakedalm.com/use-corporate-identities-existing-vso-accounts/
Other than Credit Card required 3 month trial period are there any other approach to experience Azure development.
Something like Visual Studio installed SDK?
My gut tells me there has to be, but I can't find anything.
You can use the Azure Emulator on your local dev environment. It comes with the Azure SDK.
The current version of the SDK 2.5. You can read about it: http://azure.microsoft.com/blog/2014/11/12/announcing-azure-sdk-2-5-for-net-and-visual-studio-2015-preview/
and download it here: https://www.microsoft.com/en-us/download/details.aspx?id=44938
Most of the azure can be experienced on a dev environment. It depends on which service you would like to use. You can do a search on azure documentation and you should be able to figure it out. For example, this is how you can use Azure Storage in a dev environment.
I have gone through the Lab AdvancedWebAndWorkerRoles which you have provided in the latest training kit WAPTK. I followed the steps in Exercise 1:registering sites,Applications and Virtual directories .It is running fine in windows azure emulator(locally),but i cannot find any steps to host in the windows azure management portal.
Can any one suggest(steps) how to host the same application in the windows azure management portal?
We know how to deploy applications in windows azure portal.As i had mentioned in my question about the Exercise 1:registering sites,Applications and Virtual directories in the training kit WAPTK ,we want to create the similar application and host in the azure.The steps to host the Exercise 1 application in management portal is not mentioned in the training kit.We tried to host the application in windows azure portal but it is not working as the ServiceDefinition.csdef include some different configurations.We wanted to know the steps to host that application in management portal.
Under the Introduction to Windows Azure lab, look at Exercise 3: Publishing a Windows Azure Application. This shows how to publish via the portal. The basic steps:
Build your Windows Azure service in Visual Studio, but tell it not to publish. Just generate the package file and configuration file.
Create a new hosted service. This gets a name like myapp.cloudapp.net. You'll need to find a unique DNS prefix.
Select the generated package file and configuration file, from the portal, which results in your service being launched. This takes a few minutes, and you can watch its status via the portal.
You may also publish directly from Visual Studio. See this MSDN article for instructions on setting up Visual Studio correctly (which basically imports your publishing settings from the portal). Visual Studio can perform all of the steps without having you to actually do anything in the portal (aside from exporting your publish settings).