Movatterモバイル変換

[0]ホーム
URL:

Skip to main content

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Download Microsoft EdgeMore info about Internet Explorer and Microsoft Edge
Table of contentsExit focus mode

Deploy a Python (Flask) web app with PostgreSQL in Azure

  • 2025-04-17
Feedback

In this article

In this tutorial, you'll deploy a data-driven Python web app (Flask) toAzure App Service with theAzure Database for PostgreSQL relational database service. Azure App Service supportsPython in a Linux server environment. If you want, see theDjango tutorial or theFastAPI tutorial instead.

An architecture diagram showing an App Service with a PostgreSQL database in Azure.

In this tutorial, you learn how to:

  • Create a secure-by-default App Service, PostgreSQL, and Redis cache architecture.
  • Secure connection secrets using a managed identity and Key Vault references.
  • Deploy a sample Python app to App Service from a GitHub repository.
  • Access App Service connection strings and app settings in the application code.
  • Make updates and redeploy the application code.
  • Generate database schema by running database migrations.
  • Stream diagnostic logs from Azure.
  • Manage the app in the Azure portal.
  • Provision the same architecture and deploy by using Azure Developer CLI.
  • Optimize your development workflow with GitHub Codespaces and GitHub Copilot.

Prerequisites

Skip to the end

If you just want to see the sample app in this tutorial running in Azure, just run the following commands in theAzure Cloud Shell, and follow the prompt:

mkdir msdocs-flask-postgresql-sample-appcd msdocs-flask-postgresql-sample-appazd init --template msdocs-flask-postgresql-sample-appazd up

1. Run the sample

First, you set up a sample data-driven app as a starting point. For your convenience, thesample repository, includes adev container configuration. The dev container has everything you need to develop an application, including the database, cache, and all environment variables needed by the sample application. The dev container can run in aGitHub codespace, which means you can run the sample on any computer with a web browser.

Note

If you are following along with this tutorial with your own app, look at therequirements.txt file description inREADME.md to see what packages you'll need.

Step 1: In a new browser window:

  1. Sign in to your GitHub account.
  2. Navigate tohttps://github.com/Azure-Samples/msdocs-flask-postgresql-sample-app/fork.
  3. UnselectCopy the main branch only. You want all the branches.
  4. SelectCreate fork.

A screenshot showing how to create a fork of the sample GitHub repository.

Step 2: In the GitHub fork:

  1. Selectmain >starter-no-infra for the starter branch. This branch contains just the sample project and no Azure-related files or configuration.
  2. SelectCode >Create codespace on starter-no-infra.The codespace takes a few minutes to set up, and it runspip install -r requirements.txt for your repository at the end.

A screenshot showing how to create a codespace in GitHub.

Step 3: In the codespace terminal:

  1. Run database migrations withflask db upgrade.
  2. Run the app withflask run.
  3. When you see the notificationYour application running on port 5000 is available., selectOpen in Browser.You should see the sample application in a new browser tab.To stop the application, typeCtrl+C.

A screenshot showing how to run the sample application inside the GitHub codespace.

Tip

You can askGitHub Copilot about this repository. For example:

  • @workspace What does this project do?
  • @workspace What does the .devcontainer folder do?

Having issues? Check theTroubleshooting section.

2. Create App Service and PostgreSQL

In this step, you create the Azure resources. The steps used in this tutorial create a set of secure-by-default resources that include App Service and Azure Database for PostgreSQL. For the creation process, you specify:

  • TheName for the web app. It's used as part of the DNS name for your app.
  • TheRegion to run the app physically in the world. It's also used as part of the DNS name for your app.
  • TheRuntime stack for the app. It's where you select the version of Python to use for your app.
  • TheHosting plan for the app. It's the pricing tier that includes the set of features and scaling capacity for your app.
  • TheResource Group for the app. A resource group lets you group (in a logical container) all the Azure resources needed for the application.

Sign in to theAzure portal and follow these steps to create your Azure App Service resources.

Step 1: In the Azure portal:

  1. Enter "web app database" in the search bar at the top of the Azure portal.
  2. Select the item labeledWeb App + Database under theMarketplace heading.You can also navigate to thecreation wizard directly.

A screenshot showing how to use the search box in the top tool bar to find the Web App + Database creation wizard.

Step 2: In theCreate Web App + Database page, fill out the form as follows.

  1. Resource Group: SelectCreate new and use a name ofmsdocs-flask-postgres-tutorial.
  2. Region: Any Azure region near you.
  3. Name:msdocs-python-postgres-XYZ.
  4. Runtime stack:Python 3.12.
  5. Database:PostgreSQL - Flexible Server is selected by default as the database engine. The server name and database name are also set by default to appropriate values.
  6. Add Azure Cache for Redis?:No.
  7. Hosting plan:Basic. When you're ready, you canscale up to a production pricing tier.
  8. SelectReview + create.
  9. After validation completes, selectCreate.

A screenshot showing how to configure a new app and database in the Web App + Database wizard.

Step 3: The deployment takes a few minutes to complete. Once deployment completes, select theGo to resource button. You're taken directly to the App Service app, but the following resources are created:

  • Resource group: The container for all the created resources.
  • App Service plan: Defines the compute resources for App Service. A Linux plan in theBasic tier is created.
  • App Service: Represents your app and runs in the App Service plan.
  • Virtual network: Integrated with the App Service app and isolates back-end network traffic.
  • Network interfaces: Represents private IP addresses, one for each of the private endpoints.
  • Azure Database for PostgreSQL flexible server: Accessible only from within the virtual network. A database and a user are created for you on the server.
  • Private DNS zones: Enables DNS resolution of the key vault and the database server in the virtual network.

A screenshot showing the deployment process completed.

3. Secure connection secrets

The creation wizard generated the connectivity variables for you already asapp settings. However, the security best practice is to keep secrets out of App Service completely. You'll move your secrets to a key vault and change your app setting toKey Vault references with the help of Service Connectors.

Step 1: Retrieve the existing connection string

  1. In the left menu of the App Service page, selectSettings > Environment variables.
  2. SelectAZURE_POSTGRESQL_CONNECTIONSTRING.
  3. InAdd/Edit application setting, in theValue field, find thepassword= part at the end of the string.
  4. Copy the password string afterPassword= for use later.This app setting lets you connect to the Postgres database secured behind a private endpoint. However, the secret is saved directly in the App Service app, which isn't the best. You'll change this.

A screenshot showing how to see the value of an app setting.

Step 2: Create a key vault for secure management of secrets

  1. In the top search bar, type "key vault", then selectMarketplace >Key Vault.
  2. InResource Group, selectmsdocs-python-postgres-tutorial.
  3. InKey vault name, type a name that consists of only letters and numbers.
  4. InRegion, set it to the same location as the resource group.

A screenshot showing how to create a key vault.

Step 3: Secure the key vault with a Private Endpoint

  1. Select theNetworking tab.
  2. UnselectEnable public access.
  3. SelectCreate a private endpoint.
  4. InResource Group, selectmsdocs-python-postgres-tutorial.
  5. In the dialog, inLocation, select the same location as your App Service app.
  6. InName, typemsdocs-python-postgres-XYZVaultEndpoint.
  7. InVirtual network, selectmsdocs-python-postgres-XYZVnet.
  8. InSubnet,msdocs-python-postgres-XYZSubnet.
  9. SelectOK.
  10. SelectReview + create, then selectCreate. Wait for the key vault deployment to finish. You should see "Your deployment is complete."

A screenshot showing how to secure a key vault with a private endpoint.

Step 4: Configure the PostgreSQL connector

  1. In the top search bar, typemsdocs-python-postgres, then select the App Service resource calledmsdocs-python-postgres-XYZ.
  2. In the App Service page, in the left menu, selectSettings > Service Connector. There's already a connector, which the app creation wizard created for you.
  3. Select checkbox next to the PostgreSQL connector, then selectEdit.
  4. InClient type, selectDjango. Even though you have a Flask app, theDjango client type in the PostgreSQL service connector gives you database variables in separate settings instead of one connection string. The separate variables are easier for you to use in your application code, which usesSQLAlchemy to connect to the database.
  5. Select theAuthentication tab.
  6. InPassword, paste the password you copied earlier.
  7. SelectStore Secret in Key Vault.
  8. UnderKey Vault Connection, selectCreate new.ACreate connection dialog is opened on top of the edit dialog.

A screenshot showing how to edit a service connector with a key vault connection.

Step 5: Establish the Key Vault connection

  1. In theCreate connection dialog for the Key Vault connection, inKey Vault, select the key vault you created earlier.
  2. SelectReview + Create.
  3. When validation completes, selectCreate.

A screenshot showing how to configure a key vault service connector.

Step 6: Finalize the PostgreSQL connector settings

  1. You're back in the edit dialog fordefaultConnector. In theAuthentication tab, wait for the key vault connector to be created. When it's finished, theKey Vault Connection dropdown automatically selects it.
  2. SelectNext: Networking.
  3. SelectSave. Wait until theUpdate succeeded notification appears.

A screenshot showing the key vault connection selected in the defaultConnector.

Step 7: Verify the Key Vault integration

  1. From the left menu, selectSettings > Environment variables again.
  2. Next toAZURE_POSTGRESQL_PASSWORD, selectShow value. The value should be@Microsoft.KeyVault(...), which means that it's akey vault reference because the secret is now managed in the key vault.

A screenshot showing how to see the value of PostgreSQL password in Azure.

To summarize, the process for securing your connection secrets involved:

  • Retrieving the connection secrets from the App Service app's environment variables.
  • Creating a key vault.
  • Creating a Key Vault connection with the system-assigned managed identity.
  • Updating the service connectors to store the secrets in the key vault.

Having issues? Check theTroubleshooting section.

4. Deploy sample code

In this step, you configure GitHub deployment using GitHub Actions. It's just one of many ways to deploy to App Service, but also a great way to have continuous integration in your deployment process. By default, everygit push to your GitHub repository kicks off the build and deploy action.

Step 1: In the left menu, selectDeployment >Deployment Center.

A screenshot showing how to open the deployment center in App Service.

Step 2: In the Deployment Center page:

  1. InSource, selectGitHub. By default,GitHub Actions is selected as the build provider.
  2. Sign in to your GitHub account and follow the prompt to authorize Azure.
  3. InOrganization, select your account.
  4. InRepository, selectmsdocs-flask-postgresql-sample-app.
  5. InBranch, selectstarter-no-infra. This is the same branch that you worked in with your sample app, without any Azure-related files or configuration.
  6. ForAuthentication type, selectUser-assigned identity.
  7. In the top menu, selectSave.App Service commits a workflow file into the chosen GitHub repository, in the.github/workflows directory.By default, the deployment centercreates a user-assigned identity for the workflow to authenticate using Microsoft Entra (OIDC authentication). For alternative authentication options, seeDeploy to App Service using GitHub Actions.

A screenshot showing how to configure CI/CD using GitHub Actions.

Step 3: Back in the GitHub codespace of your sample fork, rungit pull origin starter-no-infra.This pulls the newly committed workflow file into your codespace.

A screenshot showing git pull inside a GitHub codespace.

Step 4 (Option 1: with GitHub Copilot):

  1. Start a new chat session by selecting theChat view, then selecting+.
  2. Ask, "@workspace How does the app connect to the database?" Copilot might give you some explanation aboutSQLAlchemy how its connection URI is configured inazureproject/development.py andazureproject/production.py.
  3. Ask, "@workspace In production mode, my app is running in an App Service web app, which uses Azure Service Connector to connect to a PostgreSQL flexible server using the Django client type. What are the environment variable names I need to use?" Copilot might give you a code suggestion similar to the one in theOption 2: without GitHub Copilot steps below and even tell you to make the change in theazureproject/production.py file.
  4. Openazureproject/production.py in the explorer and add the code suggestion.GitHub Copilot doesn't give you the same response every time, and it's not always correct. You might need to ask more questions to fine-tune its response. For tips, seeWhat can I do with GitHub Copilot in my codespace?.

A screenshot showing how to ask a question in a new GitHub Copilot chat session.

Step 4 (Option 2: without GitHub Copilot):

  1. OpenProgram.cs in the explorer.
  2. Find the commented code (lines 3-8) and uncomment it.This creates a connection string for SQLAlchemy by usingAZURE_POSTGRESQL_USER,AZURE_POSTGRESQL_PASSWORD,AZURE_POSTGRESQL_HOST, andAZURE_POSTGRESQL_NAME.

A screenshot showing a GitHub codespace and azureproject/production.py opened.

Step 5:

  1. Select theSource Control extension.
  2. In the textbox, type a commit message likeConfigure Azure database connection. Or, select and let GitHub Copilot generate a commit message for you.
  3. SelectCommit, then confirm withYes.
  4. SelectSync changes 1, then confirm withOK.

A screenshot showing the changes being committed and pushed to GitHub.

Step 6:Back in the Deployment Center page in the Azure portal:

  1. Select theLogs tab, then selectRefresh to see the new deployment run.
  2. In the log item for the deployment run, select theBuild/Deploy Logs entry with the latest timestamp.

A screenshot showing how to open deployment logs in the deployment center.

Step 7: You're taken to your GitHub repository and see that the GitHub action is running. The workflow file defines two separate stages, build and deploy. Wait for the GitHub run to show a status ofSuccess. It takes about 5 minutes.

A screenshot showing a GitHub run in progress.

Having issues? Check theTroubleshooting guide.

5. Generate database schema

With the PostgreSQL database protected by the virtual network, the easiest way to runFlask database migrations is in an SSH session with the Linux container in App Service.

Step 1: Back in the App Service page, in the left menu,

  1. SelectDevelopment Tools >SSH.
  2. SelectGo.

A screenshot showing how to open the SSH shell for your app from the Azure portal.

Step 2: In the SSH session, runflask db upgrade. If it succeeds, App Service isconnecting successfully to the database.

A screenshot showing the commands to run in the SSH shell and their output.

Tip

In the SSH session, only changes to files in/home can persist beyond app restarts. Changes outside of/home aren't persisted.

Having issues? Check theTroubleshooting section.

6. Browse to the app

Step 1: In the App Service page:

  1. From the left menu, selectOverview.
  2. Select the URL of your app.

A screenshot showing how to launch an App Service from the Azure portal.

Step 2: Add a few restaurants to the list.Congratulations, you're running a web app in Azure App Service, with secure connectivity to Azure Database for PostgreSQL.

A screenshot of the Flask web app with PostgreSQL running in Azure showing restaurants and restaurant reviews.

7. Stream diagnostic logs

Azure App Service captures all console logs to help you diagnose issues with your application. The sample app includesprint() statements to demonstrate this capability as shown below.

@app.route('/', methods=['GET'])def index():    print('Request for index page received')    restaurants = Restaurant.query.all()    return render_template('index.html', restaurants=restaurants)

Step 1: In the App Service page:

  1. From the left menu, selectMonitoring >App Service logs.
  2. UnderApplication logging, selectFile System.
  3. In the top menu, selectSave.

A screenshot showing how to enable native logs in App Service in the Azure portal.

Step 2: From the left menu, selectLog stream. You see the logs for your app, including platform logs and logs from inside the container.

A screenshot showing how to view the log stream in the Azure portal.

Learn more about logging in Python apps in the series onsetting up Azure Monitor for your Python application.

8. Clean up resources

When you're finished, you can delete all of the resources from your Azure subscription by deleting the resource group.

Step 1: In the search bar at the top of the Azure portal:

  1. Enter the resource group name.
  2. Select the resource group.

A screenshot showing how to search for and navigate to a resource group in the Azure portal.

Step 2: In the resource group page, selectDelete resource group.

A screenshot showing the location of the Delete Resource Group button in the Azure portal.

Step 3:

  1. Enter the resource group name to confirm your deletion.
  2. SelectDelete.
  3. Confirm withDelete again.

A screenshot of the confirmation dialog for deleting a resource group in the Azure portal.

2. Create Azure resources and deploy a sample app

In this step, you create the Azure resources and deploy a sample app to App Service on Linux. The steps used in this tutorial create a set of secure-by-default resources that include App Service and Azure Database for PostgreSQL.

The dev container already has theAzure Developer CLI (AZD).

  1. From the repository root, runazd init.

    azd init --template python-app-service-postgresql-infra

  2. When prompted, give the following answers:

    QuestionAnswer
    The current directory is not empty. Would you like to initialize a project here in '<your-directory>'?Y
    What would you like to do with these files?Keep my existing files unchanged
    Enter a new environment nameType a unique name. The AZD template uses this name as part of the DNS name of your web app in Azure (<app-name>-<hash>.azurewebsites.net). Alphanumeric characters and hyphens are allowed.

  3. Sign into Azure by running theazd auth login command and following the prompt:

    azd auth login

  4. Create the necessary Azure resources with theazd provision command. Follow the prompt to select the desired subscription and location for the Azure resources.

    azd provision

    Theazd provision command takes about 15 minutes to complete (the Redis cache takes the most time). Later, you'll modify your code to work with App Service and deploy the changes withazd deploy. While it's running, the command provides messages about the provisioning and deployment process, including a link to the deployment in Azure.

    This AZD template contains files (azure.yaml and theinfra directory) that generate a secure-by-default architecture with the following Azure resources:

    • Resource group: The container for all the created resources.
    • App Service plan: Defines the compute resources for App Service. A Linux plan in theBasic tier is created.
    • App Service: Represents your app and runs in the App Service plan.
    • Virtual network: Integrated with the App Service app and isolates back-end network traffic.
    • Private endpoints: Access endpoints for the key vault and the Redis cache in the virtual network.
    • Network interfaces: Represents private IP addresses, one for each of the private endpoints.
    • Azure Database for PostgreSQL flexible server: Accessible only from within the virtual network. A database and a user are created for you on the server.
    • Private DNS zone: Enables DNS resolution of the PostgreSQL server in the virtual network.
    • Log Analytics workspace: Acts as the target container for your app to ship its logs, where you can also query the logs.
    • Azure Cache for Redis: Accessible only from behind its private endpoint.
    • Key vault: Accessible only from behind its private endpoint. Used to manage secrets for the App Service app.

    Once the command finishes creating resources and deploying the application code the first time, the deployed sample app doesn't work yet because you must make small changes to make it connect to the database in Azure.

Having issues? Check theTroubleshooting section.

3. Use the database connection string

The AZD template you use generated the connectivity variables for you already asapp settings and outputs the them to the terminal for your convenience. App settings are one way to keep connection secrets out of your code repository.

  1. In the AZD output, find the settingsAZURE_POSTGRESQL_USER,AZURE_POSTGRESQL_PASSWORD,AZURE_POSTGRESQL_HOST, andAZURE_POSTGRESQL_NAME. To keep secrets safe, only the setting names are displayed. They look like this in the AZD output:

     App Service app has the following connection settings:         - AZURE_POSTGRESQL_NAME         - AZURE_POSTGRESQL_HOST         - AZURE_POSTGRESQL_USER         - AZURE_POSTGRESQL_PASSWORD         - AZURE_REDIS_CONNECTIONSTRING         - AZURE_KEYVAULT_RESOURCEENDPOINT         - AZURE_KEYVAULT_SCOPE

  2. For your convenience, the AZD template shows you the direct link to the app's app settings page. Find the link and open it in a new browser tab.

Having issues? Check theTroubleshooting section.

4. Modify sample code and redeploy

  1. In the GitHub codespace, start a new chat session by selecting theChat view, then selecting+.

  2. Ask, "@workspace How does the app connect to the database?" Copilot might give you some explanation aboutSQLAlchemy how its connection URI is configured inazureproject/development.py andazureproject/production.py.

  3. Ask, "@workspace In production mode, my app is running in an App Service web app, which uses Azure Service Connector to connect to a PostgreSQL flexible server using the Django client type. What are the environment variable names I need to use?" Copilot might give you a code suggestion similar to the one in theOption 2: without GitHub Copilot steps below and even tell you to make the change in theazureproject/production.py file.

  4. Openazureproject/production.py in the explorer and add the code suggestion.

    GitHub Copilot doesn't give you the same response every time, and it's not always correct. You might need to ask more questions to fine-tune its response. For tips, seeWhat can I do with GitHub Copilot in my codespace?.

  5. In the terminal, runazd deploy.

    azd deploy

Having issues? Check theTroubleshooting section.

5. Generate database schema

With the PostgreSQL database protected by the virtual network, the easiest way to runFlask database migrations is in an SSH session with the Linux container in App Service.

  1. In the AZD output, find the URL for the SSH session and navigate to it in the browser. It looks like this in the output:

     Open SSH session to App Service container at: <URL>

  2. In the SSH session, runflask db upgrade. If it succeeds, App Service isconnecting successfully to the database.

    A screenshot showing the commands to run in the SSH shell and their output.

    Note

    Only changes to files in/home can persist beyond app restarts. Changes outside of/home aren't persisted.

Having issues? Check theTroubleshooting section.

6. Browse to the app

  1. In the AZD output, find the URL of your app and navigate to it in the browser. The URL looks like this in the AZD output:

     Deploying services (azd deploy)   (✓) Done: Deploying service web   - Endpoint: <URL>

  2. Add a few restaurants to the list.

    A screenshot of the Flask web app with PostgreSQL running in Azure showing restaurants and restaurant reviews.

    Congratulations, you're running a web app in Azure App Service, with secure connectivity to Azure Database for PostgreSQL.

Having issues? Check theTroubleshooting section.

7. Stream diagnostic logs

Azure App Service can capture console logs to help you diagnose issues with your application. For convenience, the AZD template alreadyenables logging to the local file system and isshipping the logs to a Log Analytics workspace.

The sample application includesprint() statements to demonstrate this capability, as shown in the following snippet.

@app.route('/', methods=['GET'])def index():    print('Request for index page received')    restaurants = Restaurant.query.all()    return render_template('index.html', restaurants=restaurants)

In the AZD output, find the link to stream App Service logs and navigate to it in the browser.

Learn more about logging in Python apps in the series onsetting up Azure Monitor for your Python application.

Having issues? Check theTroubleshooting section.

8. Clean up resources

To delete all Azure resources in the current deployment environment, runazd down and follow the prompts.

azd down

Troubleshooting

Listed below are issues you might encounter while trying to work through this tutorial and steps to resolve them.

I can't connect to the SSH session

If you can't connect to the SSH session, then the app itself has failed to start. Check thediagnostic logs for details. For example, if you see an error likeKeyError: 'AZURE_POSTGRESQL_HOST', it might mean that the environment variable is missing (you might have removed the app setting).

I get an error when running database migrations

If you encounter any errors related to connecting to the database, check if the app settings (AZURE_POSTGRESQL_USER,AZURE_POSTGRESQL_PASSWORD,AZURE_POSTGRESQL_HOST, andAZURE_POSTGRESQL_NAME) were changed or deleted. Without that connection string, the migrate command can't communicate with the database.

Frequently asked questions

How much does this setup cost?

Pricing for the created resources is as follows:

How do I connect to the PostgreSQL server that's secured behind the virtual network with other tools?

  • For basic access from a command-line tool, you can runpsql from the app's SSH session.
  • To connect from a desktop tool, your machine must be within the virtual network. For example, it could be an Azure VM that's connected to one of the subnets, or a machine in an on-premises network that has asite-to-site VPN connection with the Azure virtual network.
  • You can alsointegrate Azure Cloud Shell with the virtual network.

How does local app development work with GitHub Actions?

Using the autogenerated workflow file from App Service as an example, eachgit push kicks off a new build and deployment run. From a local clone of the GitHub repository, you make the desired updates and push to GitHub. For example:

git add .git commit -m "<some-message>"git push origin main

How do I debug errors during the GitHub Actions deployment?

If a step fails in the autogenerated GitHub workflow file, try modifying the failed command to generate more verbose output. For example, you can get more output from thepython command by adding the-d option. Commit and push your changes to trigger another deployment to App Service.

I don't have permissions to create a user-assigned identity

SeeSet up GitHub Actions deployment from the Deployment Center.

What can I do with GitHub Copilot in my codespace?

You might have noticed that the GitHub Copilot chat view was already there for you when you created the codespace. For your convenience, we include the GitHub Copilot chat extension in the container definition (see.devcontainer/devcontainer.json). However, you need aGitHub Copilot account (30-day free trial available).

A few tips for you when you talk to GitHub Copilot:

  • In a single chat session, the questions and answers build on each other and you can adjust your questions to fine-tune the answer you get.
  • By default, GitHub Copilot doesn't have access to any file in your repository. To ask questions about a file, open the file in the editor first.
  • To let GitHub Copilot have access to all of the files in the repository when preparing its answers, begin your question with@workspace. For more information, seeUse the@workspace agent.
  • In the chat session, GitHub Copilot can suggest changes and (with@workspace) even where to make the changes, but it's not allowed to make the changes for you. It's up to you to add the suggested changes and test it.

Next steps

Advance to the next tutorial to learn how to secure your app with a custom domain and certificate.

Learn how App Service runs a Python app:

Feedback

Was this page helpful?

YesNo

In this article

Was this page helpful?

YesNo