Azure resource groups give a redeploy button not sure how and when to use that. Would appreciate best practices.
In general, when we facing difficulties troubleshooting, redeploying the deployment may help.
For example, when we can't connect to Azure VM or application access to windows-based Azure VM, we can try to redeploy it. When you redeploy a VM, it moves the VM to a new node within the Azure infrastructure and then powers it back on, retaining all your configuration options and associated resources.
More information about redeploy Azure VM, please refer to this link.
By default, when we select redeploy in Azure resource group deployments, Azure will use this template to deploy this resource.
Related
I have deployed a managed application into Azure Marketplace. This application is installed with a Managed Resource Group containing multiple resources, including a Linux VM.
I have a DevOps account where I am setting up pipelines to perform automatic upgrades to my application which gets installed in my VM.
I need to find a way where every new VM (created as part of marketplace application install) is automatically configured with my DevOps pipeline.
I thought I could just export an ARM template for the VM which would include the 'Continuous Delivery' configuration, and club it to my mainTemplate.json(marketplace template). But as I checked, Azure doesn't allow that. Can someone advise on how I can achieve this?
Thanks in advance.
Questions that I have is:
How SQL Virtual machine is getting created in my azure subscription as I am not creating it through the Azure portal or neither through an ARM template?
I am installing SQL server express edition in my VM through Microsoft's site does this triggers a SQL VM resource creation in Azure as well?
How to figure out the resource creation/deployments in Azure, where to find these logs?
How to recreate this issue?
In the resource group the vm is in click Deployments:
This will give the list of deployments and hopefully give you an idea where the deployment came from.
My goal is to have a VM to run builds for Azure DevOps with a user-assigned managed identity so we can keep everything connectionStringLess.
I have just created an Azure Lab and a VM in it.
The reason for this in the lab is so we can shut it down during nights and weekends.
However, I can't find the option to assign managed identities to it.
If possible, how do I do it?
Looks the lab VM (Microsoft.DevTestLab/labs/virtualmachines) does not support MSI currently, you need to use the azure VM(Microsoft.Compute/virtualMachines).
Reference - Services that support managed identities for Azure resources.
Besides, I notice you use the lab VM for auto-start/stop reason, actually the Azure VM also supports that, see Start/Stop VMs during off-hours solution in Azure Automation, not only schedule VMs to start and stop, but also other features.
I am new here and in MS Azure as well so sorry in advance for any misunderstanding.
I have a question related to the Azure Portal and Resource Group.
I have successfully built an image, created a container where the image has been pushed and no I have ResourceGroup That I can see available on the Azure Portal.
I also successfully start App Service and I can see the attribut ResourceGroup on the AppService heading right to my correctly build on the Azure Portal.
And here is the issue...
On the AppService, there is provided URL, where your cloud app is running and I cant see anything on the URL, just bluescreen which telling me to deploy the code. BUT, the resourceGroup with the code has been linked to the App Service.
I am so confused by Azure Portal Gui... and maybe I missed some tutorial or hint on the net. Does anybody has any experiences with Azure Cloud and uploading Web App ?
I am using Trial-Account.
BR
Michal.
The "Resource Group" in Azure is a way to organize related resources together. An "App Service Plan", a "Web App", etc are individual Resources. You organize multiple individual resources into Resource Groups by placing resources that are create and/or managed together in the same Resource Group. This is generally done to organize all the resources for a particular workload to be in the same Resource Group.
To publish your application code, you need to publish the code to the App Service Web App. Resource Groups don't host code, they are just for organization. You will deploy your application code and host it within the App Service Web App.
Please refer to the documentation for further explanation on how to deploy your code to App Service, manage it, and host it there:
https://learn.microsoft.com/en-us/azure/app-service/app-service-web-get-started-dotnet
We have developed and tested our webroles in our Free trial Azure cloud.
We now have to deploy the webroles to Company A Azure cloud. Company A is open to creating IIS VMs for our deployment but will not share username/pwds with us to publish our Webroles to their cloud.
This should be a pretty common scenario, would like to hear from folks who have solved it in their deployments.
How do we publish web roles to a pre-existing VM?
This isn't how Web Roles work. A Web Role (along with any other defined roles) is essentially a bundle of code, startup scripts, binaries, etc. that are needed on the VM. The VM itself is stateless: It's started up as a fresh (up to date) copy of Windows Server, and your code is executed. Anything needing install is done via your startup scripts.
You cannot push a Web Role independently to an existing Virtual Machine. You'd need to take your actual code project (e.g. asp.net) and publish that to a pre-existing VM, without any of the Web Role scaffolding. How you do that would be up to you (and the folks who are managing these VMs).
I guess there is a confusion with different concepts.
From what I understand you have already deployed your cloud service and associated web roles to a trial azure subscription. You were able to do that because you are the admin of the subscription. If you need to deploy the same set of roles and the cloud service to one of your customers azure subscription they will need to setup your account as a co-admin so you can follow the same deployment procedure you did with your trial subscription. They don't need to give you a user/pass pair. They just need to give your LiveID or appropriate credentials a temporary co-admin permission to do the deployment on their behalf. They can do this in the azure management portal.