Azure Managed Service Identity option disabled on Linux Web app service - azure

I am trying to enable MSI on Linux Web app service using ARM template.

Currently, web app on Linux does not support Managed service identity. So, you could not use ARM template to do this.
Supported service you could check this link.
Note: Azure App Service is supported, but web app on Linux currently does not support msi.

Update for anyone happening across this.
It's supported now.

Related

how to configure Windows Service Program in azure portal (PaaS)

We have installed the windows service program in azure virtual machine. After installing the windows service that has been displayed in Services.msc - this is working fine without any issues.
But while we migrating the web application to Azure PaaS , how to configure the windows service in azure portal. Kindly provide the step by step process to achieve this.
Otherwise please provide if we have any alternate method to achieve this in azure PaaS.
Thank you in advance.
There is no "Windows Service" Paas on Azure, you need to migrate your Code to Azure Functions or Azure Appservice Webjobs.
Read more here https://mariankostal.com/2021/01/24/convert-windows-service-to-azure-function/

azure app service authentication/authorization not available

I am attempting to set up the authentication for a Google login in my Azure App Service.
However In my App Service the 'Authentication/Authorization' section is not available.
What do I need to do to enable this???
From your description it seems you are based on Linux Consumption plan (because only this host plan doesn't support authentication/authorization feature).
The solution is give your function app another host plan, such as Linux Premium plan.
This is the official document:
https://learn.microsoft.com/en-us/azure/app-service/configure-authentication-provider-aad
If you use Linux Consumption plan, then any way of authentication/authorization is impossible.

Deploy Azure Cloud Service using Azure Automation Powershell DSC

We are using Azure Automation DSC and were able to do simple things like create Automation account, create Resource group, VM creation and even able to deploy a web site on the target VM. All using powershell scripting.
How can we deploy Azure Cloud Services (web role / worker role)? what are the cmdlets? Any pointers? Please help.
What more things can be achieved using this? Moreover what limitations we can expect here.
Best Regards
Azure DSC is really focused on Azure's Infrastructure as a Service (IaaS) offering. Basically you can configure virtual servers (Windows and Linux) hosted on Azure.
To manage configurations for other services in Azure it is recommended to utilize Azure Resource Manager (ARM) which will allow you to define and configure Azure services in JSON.
Microsoft offers a lot of Quick Start ARM templates that can be accessed at the Azure Quickstart site.

Azure v2 Worker Role?

I deployed an Azure Worker Role running OWIN into a Cloud Service for very fast HTTP serving. The Cloud Service exists in the "classic" environment at manage.windowsazure.com.
I would like to deploy the same lightweight application using the new ARM bits so it can be fully managed at portal.azure.com. I don't want to use a Web Application because that includes IIS.
What is the correct Platform-as-a-Service object to use in the ARM and the new portal that gives the same performance as an old Cloud Service Worker Role?
Thanks.
There isn't a Platform-as-a-Service object to use for this in ARM. Some Infrastructure-as-a-Service options are:
Create a regular Windows Azure Resource Manager VM in the new portal and set it up as an OWIN host.
Create an Azure Resource Manager template to deploy an OWIN host to a VM or a VM Scale Set. The template would use the custom script extension and/or DSC to do the setup. This would be a good re-usable solution, but someone would need to write the template for the first time.
The lightest weight solution would be to have the server running in a Docker container on Windows. You could then choose use the VM for other purposes running in other containers or purely as a container host. Note this only runs on only runs on Windows Server 2016 Technical Preview 3. See http://anthonychu.ca/post/web-api-owin-self-host-docker-windows-containers/
Edit -
Note that Service Fabric is the recommended PaaS solution in Azure Resource Manager. It is not a direct equivalent of PaaS v1 but a rich service for developing micro-service based applications: https://azure.microsoft.com/en-us/documentation/services/service-fabric/
Not sure what you mean by V2 (new portal? ARM?). The portal is an independent tool, so I'm guessing you mean ARM. ARM doesn't support Cloud Service deployments currently, but you can still deploy either from Visual Studio (using the same interface you've used in the past, in visual studio) or from the portal, as a "classic" resource (which, underneath, uses the classic Azure management API).
In the portal, you'll find Cloud service (classic):
Now you can add a new cloud service:
And fill out the various parameters:

Setting up Windows Service bus 1.1 Management Portal

I am trying to set up Windows Service bus 1.1 on my development machine(Windows7). I configured a farm on my local machine and enabled management of Management portal while configuring the farm
I am not able to see a management portal when I browse to https:// after entering my credentials I am just getting a XML description of my farm but not any UI .
I am not sure what am I missing and the documentation does not cover anything about setting up management portal.
Any help is much appreciated.
If you only installed Windows Service Bus 1.1, you are not going to be able to use the management portal. It is a Windows Azure feature.
It is possible to get a similar management experience similar to the cloud by using Service Bus integration by installing Windows Azure Pack but it is only available for Windows Server, so the only option for your management operations on Windows 7 are PowerShell commands.

Resources