Dokumentationen

Resource

No resources have been deployed in the Azure Subscription so far. Azure offers multiple Services, each suitable for a specific purpose.

The following Services are available in Azure, for example:

  • App Service: A website hosting offering
  • Azure Functions: Serverless code execution without infrastructure management
  • Azure Container Instances: Running containerized applications without server management
  • Azure SQL Database: A fully managed relational database
  • Azure Cosmos DB: A globally distributed NoSQL and multi-model database
  • Azure OpenAI Service: AI-powered services for natural language processing and machine learning
  • KeyVault: Storage for passwords
  • Storage Account: A file storage with various functions
  • Virtual Machine: A virtual machine within Azure (Windows or Linux)

This article describes the creation of an App Service for publishing a static website as an example.

Architecture

The following diagram shows a rough overview of the architecture:

architecture-beta
    group azure(logos:azure)

    service appPlan(azure:app-service-plans)[Plan] in azure
    service app(azure:app-services)[Website] in azure
    service user(azure:users)


    appPlan:R --> L:app

    user:B --> T:app
  • As shown in the diagram, an App Service Plan is created first, which represents the foundation of the website. The plan determines which features the website can use (e.g., automatic scaling, server performance, etc.). The App Service Plan also determines the price of the website.
  • The website receives an automatically registered domain name, which is used for access.

Note

This is just one possible architecture. Depending on requirements, additional components can be deployed, such as a Load Balancer for load distribution or a database for storing user data.

A corresponding guide for creation can be found in the Web Apps tutorial.

Clarity

Over time, numerous resources can accumulate in Azure. These make navigation and clarity in the portal more difficult.

To counteract this, a naming convention should be used within the Subscription. Microsoft already offers a detailed guide for this.

Next Steps

Now that the first resource has been deployed in Azure, Alerts should be set up to monitor the availability of the resource.

Further Information