|
| 1 | +::: zone pivot="video" |
| 2 | + |
| 3 | +>[!VIDEO https://learn-video.azurefd.net/vod/player?id=e7684170-b332-4cfd-bc95-f908653b39c4] |
| 4 | +
|
| 5 | +::: zone-end |
| 6 | + |
| 7 | +::: zone pivot="text" |
| 8 | + |
| 9 | +**Microsoft Azure** is one of the world's leading cloud platforms. A **cloud platform** is a collection of services you can use over the internet instead of running everything on your own computer or server. Today, most modern applications run in the cloud, in internet-based data centers that let you store data, run code, and scale without worrying about physical hardware. Instead of buying and maintaining your own infrastructure, you use services provided by trusted platforms. |
| 10 | + |
| 11 | +Azure's trusted by organizations globally to build secure, reliable applications. With Azure, you can develop AI applications and agents that take advantage of advanced AI services and deploy them at global scale. |
| 12 | + |
| 13 | +Azure provides four core categories of services: |
| 14 | + |
| 15 | +- **Compute**: The ability to run applications, programs, and workloads in the cloud. You can think of compute as renting computers in the cloud that you can scale up or down whenever you need. |
| 16 | + |
| 17 | +- **Storage**: Services that let you save and manage data in the cloud. Storage can include files, databases, images, backups—anything you want safely stored and accessible from anywhere. |
| 18 | + |
| 19 | +- **Networking**: Tools that connect your cloud resources to each other, to the internet, or to your organization. |
| 20 | +Networking makes sure your apps can talk to each other securely and efficiently. |
| 21 | + |
| 22 | +- **App Services**: Ready‑made platforms for building, hosting, and running applications without managing the underlying servers. |
| 23 | + |
| 24 | +## Azure's organizational structure |
| 25 | + |
| 26 | +When a user gets started with Azure, their access needs to be organized and managed. Azure organizes access and management by **tenants**, **subscriptions**, **resource groups**, and **resources**. |
| 27 | + |
| 28 | + |
| 29 | + |
| 30 | +An **Azure tenant** is an organization's home base and identity in Microsoft's cloud. Having a tenant is like having an apartment unit in a large building, where the building is Microsoft cloud. Each tenant is separate and secured from others—your organization has its own locks, rooms, and controls. |
| 31 | + |
| 32 | +When a company signs up for Azure or Microsoft 365, Microsoft creates a *tenant* for them. This tenant is a dedicated and secure space where all the organization’s cloud resources live. The tenant includes users, groups, identities, and policies for managing secure access. |
| 33 | + |
| 34 | +An **Azure subscription** is a billing container for your cloud resources. One tenant can contain one or many Azure subscriptions. A subscription ties your Azure usage to a payment method (or credits for free/trial accounts) and sets boundaries for cost, quotas, and access control. |
| 35 | + |
| 36 | +**Resource groups (RGs)** are folders that hold related Azure resources so you can manage them together. One subscription can have multiple resource groups. Each resource group can have custom permissions and policies at the resource-group level. |
| 37 | + |
| 38 | +An **Azure resource** is *any individual service or object you create in Azure* such as a storage account, a database, or a Foundry resource. Each resource has a resource type, configuration settings, unique resource name and ID, and optional access controls. The resource type (for example: `Microsoft.Storage/storageAccounts`) defines the resource's behavior, capabilities, and settings. |
| 39 | + |
| 40 | +When you *configure* a resource, you choose its settings, such as: |
| 41 | + |
| 42 | +- Region (where the resource is deployed) |
| 43 | +- Performance tier (associated with cost) |
| 44 | +- Permissions and security |
| 45 | + |
| 46 | +Azure's organizational structure helps ensure clarity, security, and scalability in cloud environments. Tenants and subscriptions allow for clear separation of concerns across departments or projects. Resource groups simplify management by grouping related assets, making it easier to apply policies, monitor usage, and automate deployments. Understanding this hierarchy is essential for efficient cloud governance and cost control in Azure. |
| 47 | + |
| 48 | +## Azure portal |
| 49 | + |
| 50 | +**Azure portal**, accessible at [https://portal.azure.com](https://portal.azure.com?portal=true), is a centralized, web-based management user interface (UI) for all Azure services. It can be used to: |
| 51 | + |
| 52 | +- Create and manage cloud resources |
| 53 | +- Deploy and configure services |
| 54 | +- Monitor usage, performance, and health |
| 55 | +- Manage identities, roles, and access policies |
| 56 | +- View billing, costs, and spending patterns |
| 57 | +- Access specialized services like Microsoft Foundry |
| 58 | + |
| 59 | + |
| 60 | + |
| 61 | +You can create and manage individual resources in Azure portal. Each resource has information which is accessible through the *All resources* pane. |
| 62 | + |
| 63 | + |
| 64 | + |
| 65 | +> [!NOTE] |
| 66 | +> You can also create Azure resources **programmatically**, which means using code or scripts *instead* of clicking through the Azure portal interface. This approach is useful when you want to repeat the same setup across environments, automate deployments, or reduce manual errors. For example, instead of going into the Azure portal to create a storage account, you could run a single command in the Azure CLI or use a script that creates it the same way every time. This makes your deployments faster, more reliable, and easier to maintain—especially for larger AI applications that require many resources. |
| 67 | +
|
| 68 | +Next, learn how Azure gives you everything you need to build scalable, secure AI applications. |
| 69 | + |
| 70 | +::: zone-end |
0 commit comments