Skip to main content

Microsoft Azure Web App Service

Three steps to create a FREE web app on Microsoft Azure using Azure CLI.

  • Create Resource Group - Name: myResourceGroup
  • Create App Service Plan - Name: lthwnodejs
  • Create Web app - Name: lthwnodejs

Create Resource Group


az group create --name myResourceGroup --location "South Central US"


Create FREE App Service Plan

MUST add --sku FREE 

az appservice plan create --name lthwnodejs --resource-group myResourceGroup --sku FREE


Create Web App


az webapp create --name lthwnodejs --resource-group myResourceGroup --plan lthwnodejs

Yet another example creating a python webapp

PS F:\Projects\github\iflask> .\env\Scripts\activate
(env) PS F:\Projects\github\iflask> az webapp up --sku F1 -n iflask -l centralus
webapp iflask doesn't exist
Creating Resource group 'tuyendq_rg_Linux_centralus' ...
Resource group creation complete
Creating AppServicePlan 'tuyendq_asp_Linux_centralus_0' ...
Creating webapp 'iflask' ...
Configuring default logging for the app, if not already enabled
Creating zip with contents of dir F:\Projects\github\iflask ...
Getting scm site credentials for zip deployment
Starting zip deployment. This operation can take a while to complete ...
Deployment endpoint responded with status code 202
You can launch the app at http://iflask.azurewebsites.net
{
  "URL": "http://iflask.azurewebsites.net",
  "appserviceplan": "tuyendq_asp_Linux_centralus_0",
  "location": "centralus",
  "name": "iflask",
  "os": "Linux",
  "resourcegroup": "tuyendq_rg_Linux_centralus",
  "runtime_version": "python|3.7",
  "runtime_version_detected": "-",
  "sku": "FREE",
  "src_path": "F:\\Projects\\github\\iflask"
}
(env) PS F:\Projects\github\iflask> code .
(env) PS F:\Projects\github\iflask> az webapp up --sku F1 -n iflask -l centralus
Webapp iflask already exists. The command will deploy contents to the existing app.
Creating zip with contents of dir F:\Projects\github\iflask ...
Getting scm site credentials for zip deployment
Starting zip deployment. This operation can take a while to complete ...
Deployment endpoint responded with status code 202
You can launch the app at http://iflask.azurewebsites.net
{
  "URL": "http://iflask.azurewebsites.net",
  "appserviceplan": "tuyendq_asp_Linux_centralus_0",
  "location": "centralus",
  "name": "iflask",
  "os": "Linux",
  "resourcegroup": "tuyendq_rg_Linux_centralus",
  "runtime_version": "python|3.7",
  "runtime_version_detected": "-",
  "sku": "FREE",
  "src_path": "F:\\Projects\\github\\iflask"
}
(env) PS F:\Projects\github\iflask>

Free tier limit

PS F:\Projects\github\iflask> az webapp up --sku F1 -n iflask -l centralus
webapp iflask doesn't exist
Exceeded the limit of 1 free tier linux server farm per subscription.
PS F:\Projects\github\iflask>
Labels:

Popular posts from this blog

Powershell: Enable Firewall Log

We sometimes need to enable Windows firewall's log to troubleshoot. Here is how.
Read more

Powershell: head and tail command

Use head or tail to skim the first or last 5 lines.
Read more

[Microsoft Outlook]: Set .pst and .ost files location with ForcePSTPath Registry Key

Set .pst and .ost files location with ForcePSTPath Registry Key The ForcePSTPath registry key is supported by Microsoft Outlook 2003 and later. In Microsoft Outlook 2003 and 2007, it applies to new profiles only. Microsoft Outlook 2013 and Outlook 2016 it applies to new accounts created in a profile. Microsoft Outlook 2013 saves .pst in   %userprofile%\Documents\Outlook Files folder by default. We can change that default setting by adding a new string registry key called ForcePSTPath and set the value to the folder that we want to save those files. Set Microsoft Outlook 2013 always save new .pst and .ost files to D:\Data\Mail folder OST file reached the maximum size The OST File Has Reached The Maximum Size
Read more