I created a VM in Azure and attached a cloud service (abc1.cloudapp.net) to it. So I'm able to ssh into the machine using this cloud service. Now for some reason I want to change it to (xyz.cloudapp.net).
Is this doable?
You can't change the alias for the cloud service. You will need to drop it and create a new one.
I suggest redirecting your original domain the VIP Azure provides so you have a consistent domain name all the time.
Related
I would like to associate/add a Virtual Network to a Cloud Service in Azure.
I have found a solution where you can download and edit the Cloud Service's configuration file and upload it back in order to add a Virtual Network. But the solution only works if the Cloud Service is NEW and only about to be created
However, I am trying to look for ways on how to add a Virtual Network to an already existing/running Azure Cloud Service.
Is this possible?
Unfortunately, this is not possible, whenever you want to include a cloud service on Microsoft Azure to a Network you should do it at the time it gets created, that's why it's recommended to START your project while putting all of your resources on the same network and in the same region.
I need server to setup Zumero Sync on it , I already used azure free trail now I need to upgrade but don't know if I need only to buy VM or Cloud service with it , it's not clear how to use the VM , is it like VPS ?
You can upgrade to Pay as you go subscription model which means you have to pay for what you use so in your case you have to pay for the VM and storage for storing the VHD of the VM. Cloud Service is basically a shell under which you deploy a VM so you don't need to pay for it.You can minimize the cost by shutting down the VM when not in use.
If you're not using Azure Resource Managed (announced recently by MS: IaaS Just Got Easier) the portal (and PowerShell) forces you to create a Cloud Service otherwise there's no way for you to assign an external DNS to connect to your VM. You won't need to do anything with it other than set it up if you're using a VM, but it will need to be there.
If you're not using a VM, your Cloud Service is the container for your deployment, which means you don't need to worry about maintaining IIS or Windows (which your app still runs on in the background).
I have purchased a Pay-As-You-Go Azure Subscription with the lowest resources (A0 Basic, shared core and 768 MB RAM) and automatically, four services were created for me: a Storage Account, a Virtual Machine, a Cloud Service and a Directory.
On the Virtual Machine I set up my own HTTP server software written in C# using HttpListener class. I added an HTTP Endpoint connecting the private and public port 80 on TCP. Once I've done that, I was able to access my Cloud Service address (Something.CloudApp.net).
I've created a separate Cloud Service on top of 4 service I already had and now I can't figure out how to make that service use the Virtual Machine so I can access the same HTTP server from both DNS names (Something.CloudApp.net versus SomethingElse.CloudApp.net).
The service status of both services is Created if I investigate in the Microsoft Azure Portal, however, only the first service says Running in Production column in Cloud Service list. The other one doesn't. None of the Cloud Services say anything in the Staging column.
I figure I have to set the other service to run in production too, but when I want to do that, the Portal says "You have nothing deployed to the production environment.", "Upload a new production deployment", which opens a dialog prompting me to provide details for a production environment to be newly created.
Is there a way I can make my other Cloud Service use the production environment of the first service?
Is there an alternative way to make my Virtual Machine accessible through two DNS names offered by Azure (CloudApp.net)?
The cloud service is the logical container for the VM and a VM can only be in one cloud service. There is no way to get 2 different *.cloudapp.net URLs to point to the same VM. What you can do is register 2 custom domain names (www.mydomain1.com, www.mydomain2.com) and use CNAME or A Record to point both of them to the same VM.
By default, the naming conventions of Azure websites/webapps are somesubdomain.cloudapp.net and somesubdomain.azurewebsites.net. If I have an existing website that I have currently hosted through, say GoDaddy, and the website is www.mysite.com, how can I tell the registrar (DNS) to look at Azure's servers for the website content (I have experience in changing the nameservers to point to a particular web hosting company's nameservers, but it appears that there isn't a such thing with Azure).
Ultimately what I want to do is go to www.mysite.com and have the content hosted on Azure, running on Azure's VMs. Is the only way to mess with the CNAME, A, etc. properties of the DNS?
I have a VM on Azure that I want to use to host my websites. This is the platform that I will be using. I'm not using an Azure "website" or a "cloud service".
Yes, the only way to get this working as you describe it is to fiddle with the DNS, with a CNAME and A records.
A good description of how this is done can be found here:
http://www.windowsazure.com/en-us/develop/net/common-tasks/custom-dns/
There is an official documentation, relatively easy to find with a simple internet search:
How to use custom domain with Cloud Service and Storage Account
How to use custom domain with Azure Web Sites
EDIT
One thing good to remember is that a Windows Azure Virtual Machine (IaaS) runs in a Cloud Service. Meaning that for each VM, or set of VMs you have a cloud service created (i.e. mywhateverVM.cloudapp.net). This cloud service is implicitly created when you use the portal wizard to create the VM. Or explicitly (you create it) when you create VMs with PowerShell.
So the "How to use custom domain with Cloud Service" applies also for the Azure VMs with no change at all.
Given:
Couple of websites created using Azure Web Sites execution model.
No RDP access since Azure Web Sites doesn't provide it.
Possibility to install/create Cloud Service on Azure. Cloud Service
does have RDP access to its websites.
Question:
Will it be possible to access the existing websites via RDP on Cloud Service?
Assuming you had deployed your sites in Azure Cloud Services and enabled RD, you can very well look at the setup and config of your site(s) under it.
However if you make any changes, it may not be reflected to the setup as the Azure Cloud Services is non persistent and during any Data center activities like load balancing the fabric controller may just pull of your instance and re-deploy in someother instance. During this process all your changes will be lost and the original package of cscsf and cscfg will utilized during deployment.