I am starting to create Azure Data Factories at my company. Primarily loading data from our on-premise SQL databases to Azure SQL Data Warehouse. However, I am only able to publish them from the Microsoft Azure web portal, and not Visual Studio 2015. When I right-click on the project in Solution Explorer and select the publish button, I am asked to login to MS Visual Studio. After logging in on the Data Factory Configuration page, I cannot see any existing data factories nor create any new ones. The Use existing Data Factory Name, Subscription, Resource Group, and Region drop downs are disabled (see screenshot).
I am the owner of the Data Factory and have not had any other issues publishing or running pipelines in the data factories I create. I am the sole developer on the team working with data factories and the person who set me up and configured our Azure services cannot find the problem either.
I imagine it is a configuration issue or something to do with my account. I have re-installed VS2015 Enterprise from scratch to no avail. Any suggestions?
You need to have co-admin or admin privileges on atleast one subscription to be able to create or use existing Data Factories. The permissions should be granted using the old management azure portal. If co-admin privileges provided using new portal it wont work.
Thanks
Vijay
Open View->Other Windows->Data Factory Task List. There should be log of your operations. It looks like this:
Data Factory Task List
If you double click on entry there is more detailed task log
Related
Using SQL Server Management Studio I have created a SQL User in my Synapse serverless database using the following syntax
CREATE USER [app-myappnameadsgsdaga-uat-westus] FROM EXTERNAL PROVIDER
(This is an Azure AD application)
After creating the user I see the login listed in SSMS under security/users:
When I browse the same database using Synapse Studio, I see the user listed multiple times:
Is this a bug in Synapse Studio, or am I creating the user in the wrong way?
Did you try refreshing databases in Synapse Studio and/or workspace?
If that didn't help, please create a support ticket. You can do this by navigating to feedback and then click on "Contact support" where you will have an option to add the description of your issue.
Thanks!
I am using azure machine learning services. I have created an experiment and deployed as a webservice on Azure Machine Learning Workspace.
My problem Is my subscription has expired and now I want to export/move my Azure Machine Learning Workspace to different subscription so I can reuse its all content(model, experiment etc.) without losing.
How can I save my all important work and export or move Azure Machine Learning Workspace with all working functionalities in different subscription?
Thank you
Regards,
Ahmad
The following document demonstrates how to migrate Azure resources across subscriptions. You should be able to migrate your workspace as indicated here.
As highlighted in the document above, if the tenant IDs for the source and destination subscriptions aren't the same, use the following methods to reconcile the tenant IDs:
Transfer ownership of an Azure subscription to another account
How to associate or add an Azure subscription to Azure Active Directory
The source and destination subscriptions must be active. If you have trouble enabling an account that has been disabled, create an Azure support request. Select Subscription Management for the issue type.
This document says that moving an AML workspace is currently not supported:
https://learn.microsoft.com/en-us/azure/machine-learning/how-to-manage-workspace
In this doc referenced in a previous answer, .MachineLearning refers to the classic ML studio. You should be looking for .MachineLearningServices which refers to the new AML studio which clearly states that moving between resource groups or subscriptions is not supported.
I'm looking to do this myself but I haven't found a complete solution.
I want to move my WPF application project from a private Azure Devops account to an organization account.
So I thought I'd just create a new project in the Azure portal and push my code to that project instead.
But when I start to configure a new project I can't select "Windows application" or anything similar to that, only web applications are available. And it want's to deploy to an Azure service which you can't deselect! So here is where I want to close the window and move to AWS.
I don't want to deploy my application or set up any servers. I just want to start a new organization project. A totally empty if nothing else!
Thanks!
Create your project within your Azure DevOps web portal, (https://dev.azure.com/YourOrganization), not the Azure portal.
There's a lot of terminology confusion because Azure DevOps was/is an independent Microsoft service called "Visual Studio Team Services" up until recently. It's been brought under the Azure umbrella and rebranded, but an Azure DevOps account has its own totally separate interface, which is where you should do most day-to-day operations.
I used Microsoft SQL Server Management Studio 2016 to deploy my database to Azure and everything went OK with no problem and it managed to create the database on Azure however the imported database is not visible outside the Azure SQL Server(Web portal) as a standalone resource and also when I try to access it within the Azure SQL server it complains : "Access denied".
What is the difference between this database and the one I create using web portal? If I create the database in web portal it will be visible as a standalone resource in the resource group but importing it from management studio only makes it only visible inside the sql management studio.
Should I add any special permission from the management studio to this newly imported database to make it visible inside the web portal?
Update 1 : Just realised that this behaviour only happens when I choose UK South region. West-Europe databases can be created and accessed using both Web portal and SSMS with no problem.
Update 2 I tried creating the database in North Europe region and did not have any problem either. This issue needs to be resolved by the UK-South region SQL Azure Team.
you are correct, there was a configuration issue where for a period SQL Databases created in the Azure UK South or UK West regions via T-SQL (such as via SSMS), via the old portal, or via the older service management APIs or PowerShell may not have been visible in the Azure Management portal (portal.azure.com). Affected databases were online and fully accessible to applications throughout. The issue has now been resolved and impacted customers were notified. We are taking steps to improve the validation of configurations to prevent a recurrence of this. We apologize for the inconvenience.
This issue has been resolved now and the databases in UK South region can be happily deployed from SQL Server Management Studio and they are fully accessible in the web portal.
Without linking the database, the website is able to connect to the database.
Well then, when should I link the database to the website?
Linked Resources are a way of providing context to the portal about which Services belong to your deployed application. This enables the context for those service items to be added to your publishsettings file. The publishsettings file is used by visual-studio, webmatrix as well as the Windows Azure CLI Tools and Windows Azure Powershell Tools to import attributes of your subscription.
You can use a Linked Resource to add a SQL Database database to your web site.