On Azure, I am currently using my "3-month Free Trial" subscription, and just recently I got access to a "Windows Azure MSDN - Visual Studio Ultimate" subscription.
Is it possible to move an existing set of hosted sites to another subscription using the Portal?
Obviously I could just re-publish the sites using Visual Studio, but I'm wondering if there is a way to do this in the GUI?
There is no way you can accomplish in the Portal interface. You do have an option to request Windows Azure Billing Team and request them move all of your currently configured and running services from one Subscription to other subscription, the key is "all".
IF you want to move one specific service from one subscription to another then the available option is to deploy directly to other subscription.
I did do this once. I had to contact their billing team and after a couple of days of back and forth between them it was taking too long so I just did it manually, redeploying the sites to the new subscription. This may not be possible if you have many sites. I did a backup and restore of the SQL Azure database.
I am battling with azure support right now on trying to do the same thing. From what I can tell your best bet is creating the services on your MSDN subscription and redeploying.
I don't know a way to do this from the portal but I do recommend using Windows Azure PowerShell which has the ability to manage multiple subscriptions and in your case you can just do this cmdlet to copy a service into another subscription:
Publish-AzureServiceProject -sn MyNewSubscriptionName
Related
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 have an SharePoint Office 365 Developer account and initially it was created using #xyz.onmicrosoft.com account.
Now I have added #xyz.com. All the billing management happen using the admin#xyz.onmicrosoft.com and application access happen using user#xyz.com
Now I am planning to add Azure Pay-As-You-Go subscription but I am confused should I create the Azure portal account using admin#xyz.onmicrosoft.com or user#xyz.com
Is there any best practice or general recommendation available ?
this is completely up to your organization, there are no major advantages of using one or other.
Nevertheless, an "user#xyz.com" account will be friendlier than "user#xyz.onmicrosoft.com".
What is the difference between these two portals and why? And when should I use which of them?
For example:
When I want to configure if/which Java version I want to use in a WebApp, in the "manage"-portal I only can choose between off and v1.7.0_51. In the "portal"-portal I can choose between off, v7 and v8.
Or, if I want to create a new Ubuntu-VM, in the "manage"-portal I can choose between v12.04, v14.04 and v15.04. In the "portal"-portal there is only v14.04.
As commented by Mike, manage.windowsazure.com is the current production Azure Portal while portal.azure.com is the preview portal which will eventually replace the production portal.
From an underlying technology perspective, there's one big difference between the production and preview portal. Production portal makes use of Azure Service Management API while the Preview portal makes use of Azure Resource Manager (ARM). Along with ARM API, you get Role-based access control (RBAC) that enables you to grant granular permissions on your Azure resources to your team members. In the production portal, there's only a concept of Subscription Administrator and Subscription Co-Administrator.
Not all services in Azure has been ported to make use of ARM API as of today and that's why you see only few services in the preview portal. Services that make use of ARM API (all the new services) will only show up the preview portal.
As to when to use what portal, just see the Azure services you need to manage. Based on how they can be managed, you will choose between production and preview portal. Also please note that functionality for a service may differ between portals even though it is present in both portals. That may be another criteria between choosing the portal.
More information Can be find from microsoft site
Azure Resource Manager vs. classic deployment: Understand deployment models and the state of your resources
I'm currently stuck with designing my Azure environments.
What i would like to have is multiple Azure subscriptions that work togheter in a private network with Active directory on the different subscriptions that are synced.
Imagine the following scenario:
I've got two developers, who each have an own Azure Subscription (free with msdn) on which they develop their software.
When they finished the code, they will do a checkin to a visualstudio online and a build server on a second azure subscription will build the code.
When everything is ok, the code will be deployed on a VM in a third subscription.
All this would need to work with synced active directory's and in a private network.
This means that if their is a website created in the thrid subscription, it would only be accesible from a VM in subscription 1 or 2
So as resume:
1 subscription for the developer to developer code (visual studio, AD, sql, ...)
1 subscription for building the code of the developer
1 subscription for collect all the code and test the software (AD, SQL, website, ...)
Only subscription 1 should be able to access VM's, websites, ... in subscription 2 or 3.
Could any of you advise how I should set up the Virtual network, VPN, ...? Or maybe is just not possible?
Thanks in advance!!
Today's Virtual Network feature does not let you span data center regions, subscriptions, etc. as far as I know, sorry!
I'm sure people are looking at what it would take to support this sort of scenario someday.
I'd recommend to look at Azure VNet-to-VNet VPN gateway. It works fine through different regions and Azure subscriptions.
I want to outsource the development of a WordPress website that will be hosted in Azure. Is there a way to create a Cloud Service that I can give someone access to, but at the same time not giving them my Azure subscription credentials?
From an Azure subscription perspective, you can only grant co-admin privilege; a co-admin gets full access to a subscription. This leaves you with a few options (I'm sure you can think of others):
Set up a separate subscription solely for the outsourced WordPress work. At completion of project, you can choose to remove the co-admin rights of the subscription
Grant admin access to the WordPress site, along with specific Azure resource keys (e.g. storage account namespace+key; service bus, MySQL credentials, etc.) for your developer to do the work. You can always change access keys once the project is completed
Have your developer set up WordPress in their own subscription, and then transfer the contents to your subscription when the project is complete.
EDIT - I slightly misunderstood the question, and was thinking the outsourced dev needed certain subscription-level resources. As Mike pointed out, source control is a good solution for Web Sites. You'd still need to set up resources such as Storage accounts if you don't want to set them up as co-admin.
If you are using Cloud Services then you could set up continuous integration between TFS and your cloud service. This would allow you to give the other person their own accounts to your TFS source code. Thus they check in and trigger the build, and it deploys. They don't have access.
If you don't have to have Cloud Service then you also have the same option with Windows Azure Web Sites (it's under development so this should be fine to run in even under the free, and bump up if you want to load test, etc.). With that you can give ftp access only, or also set up TFS or GIT source control integration.