Created a VM image in azure classic portal, then used that image file to create vm and generated a test report using azure certified test tool.
Publish the VM image in Azure publish portal https://publish.windowsazure.com
It is in 0% of progress in staging state and also shows the below error message with it.Failure: SAS url is not well formed. (Requires Publisher Action)
I could not stop the staging process and there is no option to delete the virtual machine details in azure publish portal.
Also it is not showing option to upload test report of vm image.Please let me know if there is any solution for this.
I've seen this before when creating the SAS url using the latest version of storage explorer. Try using version 6 to create the url and push to staging again (a new request).
Related
I know that question is rather amateur but I hope someone will give me a hint what I did it wrong.
I'm using:
Azure SQL Server database - I can access it from Azure db instance from my local SSMS
Azure App Service - also created, up and running
VS22 deployment => Publish => connect to my Azure account, and imported publish profile.
Deployment went well: and the code in release mode is published to Azure App Service.
But I can't see my Swagger page on my Azure website.
I'm using .NET 7
Maybe you can tell me what I'm missing here? Maybe I need to wait for instance of azure app service to be created? although I can access it and use all features that I paid.
Also, my logs are empty
I created a sample webapp in visual studio 2022 using .net 7
Image for reference:
I connected to my Azure sql database from SSMS to the webapp using visual studio.
Image for reference:
It connected successfully. I published it to Azure through Visual studio 2022.
For that I created an app service in azure.
Image for reference:
published into that APP.
Image for reference:
It published successfully.
Image for reference:
It run successfully after deployment.
In portal I go to API-->Api management and created new api for my app.
Image for reference:
I linked the Api Management and click on the Api which I created I got the swagger page
Image for reference:
In this way we can find the swagger page for an App in azure portal.
I am using an Azure DevOps pipeline that is basically a series of steps that call PowerShell scripts that take in parameter values and within the PS script the "Az module commands" are called - these commands create the infrastructure on Azure.
For example...
Create a public static IP address - this I can do.
Create a NIC and link static IP address - this I can do.
Create a Synapse Workspace and 'Self Integration Runtime' - this I can do accept link Synapse SHIRT to the self-hosted integrated runtime on the Azure VM.
Create a Windows VM (datacenter 2019) - this I can do.
Create a Azure Windows VM self-hosted integration runtime via devOps pipeline???
I now want to create a step in the devOPs pipeline (maybe an ARM template or PS script that calls an Az module) that automatically installs the 'self hosted integration runtime' on the Azure Windows VM - the VM is attached to an Vnet/subnet. The runtime on the Azure VM will be linked to the Synapse runtime. (note I am not using Data Factory)
I have read the following. But can't workout if setting up a runtime on the Azure VM and Synapse and linking them is possible and if it can be automated in a devOPs pipeline?
https://learn.microsoft.com/en-us/azure/data-factory/create-self-hosted-integration-runtime?tabs=data-factory#considerations-for-using-a-self-hosted-ir
The below link is very near to what I want to achieve....
https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.compute/vms-with-selfhost-integration-runtime
Have added one manually step once the devOps pipeline finishes.
Open RDP port on Azure VM. I know the admin. username and password. Log on to the Azure VM.
Turn off advanced security features on the VM temporally.
Download and install the SHIRT from the Microsoft web-site.
Config. SHIRT with the "Key1" value from the SHIRT in Synapse.
Turn on advanced security features on the VM temporally.
I mark this site down -2 for poor editing buttons, worst I seen in 25 years in IT.
I have created a custom OS images on Azure containing my app, omsagent, and a configuration file to track my application logs. I verified that the custom logs were available on Log Analytics Workspace for that VM.
When I create a new VM with this custom OS, using Python SDK, I don't receive logs in the workspace. I verified that omsagent is working. It is sending heartbeats that are visible on the Log Analytics Workspace > Insights > Agents.
I found out that the new is was not Connected to the workspace.
So my question is how do I automatically connect a VM to Log Analytics Workspace at creation time?
I would advise against baking the Log Analytics Agent (OMS Agent) into the image directly - Azure doesn't recommend this kind of setup. Instead, you should be using an Azure Policy that they provide exactly for this scenario.
We have dozens of VMs and Scale Sets we need to manage with Log Analytics Agent installed on each of them when we build the custom images. In the beginning everything was working fine but a couple of months later those images stopped working.
After spending some time investigating with the Azure team we found out that the agent's certificate wasn't being renewed and it wouldn't connect to the Workspace automatically. Even worse was that because of this, it was failing all our images builds.
We were told that this is not the right practice and we should look at Azure Policies. They are rather easy to setup - just assign once and forget about them. It's also good for compliance and will let you know if there's any machine that's non-compliant.
Check this link for more info about Azure Monitor policies.
And this link will open your Azure Portal directly into the policies page for Windows VMs.
Here's a preview of the policies available:
Can you point me to a url which describes proper SCM for a Static Website deployed to a Storage Account? I have a ReactJS website deployed as a static website to an Azure Storage Account. Currently I'm just pushing updated deployments via an Azure extension in VS Code.
Separately, I have an App Service which has an associated Deployment Center with a configured Pipeline and its own Azure DevOps source code repo. The App Service setup as I've described seems to have at least a decent start on some semblance of SCM.
When viewing the webpage for a storage account in the Azure portal, I don't see a "Deployment Center" left nav item like I do for an App Service in the portal. In the Azure portal, looks like a storage account can only have a single static website b/c "static website" exists as a single left nav item for a particular storage account page in the Azure portal. If I click on the "static website" left nav item for my deployed ReactJS app, I don't see any type of additional hook into the Deployment Center. A "git status" on my local code folder indicates that the folder is not a git repo.
So I'd like to get my static website code into an Azure DevOps repo. I need the code to be source-controlled and since my App Service is in an Azure DevOps repo, I'd like the same for my static website code for consistency. I'm also assuming that the code needs to be in an Azure DevOps repo in order to easily and fully leverage Azure DevOps functionality like pipelines, etc.
So can you advise how I can get from point A to point B for this scenario or if there may be constraints or alternatives with what I'm trying to achieve here?
You can make use of Azure File Copy task to push the build artifacts to Blob Storage. From the documentation link:
Use this task in a build or release pipeline to copy files to
Microsoft Azure storage blobs or virtual machines (VMs).
The task is used to copy application files and other artifacts that
are required in order to install the app; such as PowerShell scripts,
PowerShell-DSC modules, and more.
You would need to push the artifacts to $web blob container as this container is used to serve static website.
You can learn more about it here: https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-file-copy?view=azure-devops
I'm new in Azure and trying to add a custom application in my azure RemoteApp. I have created an Azure VM (windows 2012 R2 Evaluation) and an azure RemoteApp collection. I have added my custom application in VM at path c:\Customs\MyTestApplication\TestApplication.exe and also in remoteapp collectio have published this custom via path %SYSTEMDRIVE%\Customs\MyTestApplication\TestApplication.exe.
But when I am runing Azure RemoteApp client I see my test application but cannot run. It cannt find the test application.
Can anyone help me please? I have spend a lot of time in azure documentations without any success.
I think I must to connect my Azure VM in azure remoteapp collection but I don't know how!
Thank you
you are close, you must create a custom image and then import that image into azure RemoteApp image library and then create a Azure RemoteApp collection specifying that image. Read here for more information = https://azure.microsoft.com/en-us/documentation/articles/remoteapp-imageoptions/