Skip to content

Commit 7fa4f48

Browse files
authored
Merge pull request #298126 from MicrosoftDocs/main
4/11/2025 AM Publish
2 parents d215047 + b1c88ae commit 7fa4f48

File tree

57 files changed

+217
-167
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

57 files changed

+217
-167
lines changed

articles/app-service/quickstart-wordpress.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,7 @@ keywords: app service, azure app service, wordpress, wordpress hosting, azure wo
66
author: msangapu-msft
77
ms.subservice: wordpress
88
ms.topic: quickstart
9-
ms.date: 02/21/2025
10-
# ms.devlang: wordpress
9+
ms.date: 04/11/2025
1110
ms.author: msangapu
1211
ms.custom: mvc, linux-related-content
1312
---
@@ -29,6 +28,8 @@ To complete this quickstart, you need an Azure account with an active subscripti
2928

3029
1. <a name="wordpress-setup"></a>Under **WordPress setup**, choose your preferred **Site Language**, then type an **Admin Email**, **Admin Username**, and **Admin Password**. The **Admin Email** is used for WordPress administrative sign-in only.
3130

31+
1. (_Optional_) Select the **Add-ins** tab. Recommended settings (including Managed Identity) are already enabled by default. Clear the checkboxes if you're unfamiliar with these settings. See [Configure WordPress add-ins](#configure-wordpress-add-ins) for more information.
32+
3233
1. Select the **Review + create** tab. After validation runs, select the **Create** button at the bottom of the page to create the WordPress site.
3334

3435
:::image type="content" source="./media/quickstart-wordpress/09-wordpress-create.png?text=WordPress create button" alt-text="Screenshot of WordPress create button on Azure App Service.":::
@@ -54,6 +55,15 @@ When no longer needed, you can delete the resource group, App service, and all r
5455

5556
:::image type="content" source="./media/quickstart-wordpress/delete-resource-group.png" alt-text="Delete resource group.":::
5657

58+
## Configure WordPress add-ins
59+
60+
In the Add-ins tab, recommended settings are already enabled by default:
61+
- Managed Identities remove the overhead of managing sensitive credentials to access Azure resources, making your website highly secure.
62+
- Azure Communication Service enables application-to-person, high-volume emails with Azure Communication Services.
63+
- Azure Content Delivery Network helps in improving performance, availability, and security by using a distributed network of servers that can store cached content in point-of-presence locations, close to end users.
64+
- Azure Front Door (AFD) provides dynamic site acceleration that reduces response times while also allowing content delivery by caching at nearest edge servers for faster media downloads.
65+
- Azure Blob Storage allows you to store and access images, videos and other files. This effectively reduces the load on your web server thereby improving performance and user experience.
66+
5767
## Manage the MySQL flexible server, username, or password (optional)
5868

5969
- The MySQL Flexible Server is created behind a private [Virtual Network](../virtual-network/virtual-networks-overview.md) and can't be accessed directly. To access or manage the database, use phpMyAdmin that's deployed with the WordPress site. You can access phpMyAdmin by following these steps:

articles/app-service/webjobs-create.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,6 @@ If instead of the Azure App Service, you're using Visual Studio to develop and d
2828

2929
WebJobs is a feature of [Azure App Service](index.yml) that enables you to run a program or script in the same instance as a web app. All app service plans support WebJobs. There's no extra cost to use WebJobs.
3030

31-
[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
32-
3331
You can use the Azure WebJobs SDK with WebJobs to simplify many programming tasks. For more information, see [What is the WebJobs SDK](https://github.com/Azure/azure-webjobs-sdk/wiki).
3432

3533
Azure Functions provides another way to run programs and scripts. For a comparison between WebJobs and Functions, see [Choose between Flow, Logic Apps, Functions, and WebJobs](../azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md).
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: Mission critical workload labeling
3+
description: Understand how to label mission critical workloads in Azure for Microsoft workload assessments
4+
ms.topic: conceptual
5+
ms.date: 03/20/2025
6+
---
7+
# Mission critical workload labeling
8+
9+
Azure provides a robust, scalable cloud platform with various tools and services to help you manage and optimize your resources. This document outlines how to tag resources in an Azure tenant for identifying mission-critical workloads and determining potential resiliency improvements. Tagging your resources streamlines the onboarding of your workload definition for Microsoft assessments, providing a more concisely targeted review.
10+
11+
## Understanding Azure tags
12+
13+
For an introduction to tagging of Azure resources and to learn about requirements and limitations refer to the following article.
14+
15+
[Use tags to organize your Azure resources and management hierarchy - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources)
16+
17+
## Why identify mission critical workloads?
18+
19+
Identifying mission critical related resources brings numerous benefits including resource management, cost management and optimization, security, automation and workload optimization. By tagging these resources, you can group them as part of a mission critical workload. These tags help in accurately identifying and managing these essential workloads. You can read more about tagging usage here [Resource naming and tagging decision guide - Cloud Adoption Framework | Microsoft Learn](/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming-and-tagging-decision-guide).
20+
21+
This article aligns with workload optimization, where tagging can help inform of opportunities to improve resiliency and further enhance your Service Level Objectives.
22+
23+
*This documentation supports a Microsoft assessment of your environment using the tagging approach described. Your Microsoft contact reviews this tagging approach with you at the beginning of the assessment. If you don't have an engagement with Microsoft, you can still follow the guidance to realize the benefits outlined earlier.*
24+
25+
The term workload refers to a collection of application resources that support a common business goal or the execution of a common business process, with multiple services, such as APIs and data stores, working together to deliver specific end-to-end functionality.
26+
27+
Mission critical workload resources are often spread across multiple resource groups and subscriptions. Regardless of the resource location, each resource within the mission critical workload should be included in the workload definition and tagged appropriately.
28+
29+
In a scenario where a mission critical workload depends on a service that is shared across multiple workloads, such as an ExpressRoute gateway or an Azure Firewall, the shared resources should also be included in the workload definition and tagged appropriately. See the example in the previous section for tag values to be used on shared services.
30+
31+
For further insights into defining a workload, refer to the following article.
32+
33+
[Azure Well-Architected Framework workloads - Microsoft Azure Well-Architected Framework | Microsoft Learn](/azure/well-architected/workloads)
34+
35+
## Mission critical predefined tags
36+
37+
To enable use by Microsoft in a workload assessment, the tags used for mission critical workloads must use the following tag name and adhere to the value format.
38+
39+
> [!Important]
40+
> Tag values must **NOT** contain numeric or non-English characters.
41+
> Tag values must conform to this RegEx pattern: ^[A-Za-z]+-[A-Za-z]+
42+
43+
| **Tag Name** | **Value Type** | **Purpose** | **Value Format** |
44+
|---|---|---|---|
45+
| **Azure.MissionCriticalWorkload** | String | Workload | DeptName-WorkloadName |
46+
| **Azure.MissionCriticalWorkload** | String | SharedServices | SharedServices-Service |
47+
48+
### Examples
49+
50+
#### Mission critical workload #1
51+
52+
| **Workload Component** | **Tag Name** | **Tag Value** |
53+
|---|---|---|
54+
| **Workload A** | Azure.MissionCriticalWorkload | Finance-Workload |
55+
| **Shared Services** | Azure.MissionCriticalWorkload | SharedServices-ExpressRoute |
56+
57+
#### Mission critical workload #2
58+
59+
| **Workload Component** | **Tag Name** | **Tag Value** |
60+
|---|---|---|
61+
| **Workload B** | Azure.MissionCriticalWorkload | HR-Workload |
62+
| **Shared Services** | Azure.MissionCriticalWorkload | SharedServices-Firewall |
63+
| **Shared Services** | Azure.MissionCriticalWorkload | SharedServices-ExpressRoute |
64+
65+
## How to apply Azure tags
66+
67+
Tagging of mission critical workloads requires that tags be applied to each of the individual Azure resources that make up the workload. Tags can be applied to resources in the Azure portal, with Azure Policy, or via automation tools. Review the following guidance to determine the approach that works best for your organization.
68+
69+
- Azure portal: [Tag resources, resource groups, and subscriptions with Azure portal - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-portal)
70+
- Azure Policy: [Policy definitions for tagging resources - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-policies)
71+
- Azure PowerShell: [Tag resources, resource groups, and subscriptions with Azure PowerShell - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-powershell)
72+
- Azure CLI: [Tag resources, resource groups, and subscriptions with Azure CLI - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-cli)
73+
- Bicep: [Tag resources, resource groups, and subscriptions with Bicep - Azure Resource Manager | Microsoft Learn](/azure/azure-resource-manager/management/tag-resources-bicep)
74+
- Terraform: [Microsoft.Resources/tags - Bicep, ARM template & Terraform AzAPI reference | Microsoft Learn](/azure/templates/microsoft.resources/tags)

articles/azure-resource-manager/management/tag-resources-bicep.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.date: 09/26/2024
1111
This article describes how to use Bicep to tag resources, resource groups, and subscriptions during deployment. For tag recommendations and limitations, see [Use tags to organize your Azure resources and management hierarchy](tag-resources.md).
1212

1313
> [!NOTE]
14-
> The tags you apply through a Bicep file overwrite any existing tags.
14+
> The tags you apply through a Bicep file will replace any existing tags on the resource. If you want to retain existing tags, you need to explicitly include them in the template.
1515
1616
## Apply values
1717

articles/azure-resource-manager/management/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -161,6 +161,8 @@
161161
href: tag-support.md
162162
- name: Azure Resource Graph queries
163163
href: ./resource-graph-samples.md
164+
- name: Mission critical workload labeling
165+
href: tag-mission-critical-workload.md
164166
- name: Private link access
165167
items:
166168
- name: Create - portal

articles/azure-web-pubsub/reference-mqtt-cross-protocol-communication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Here's the conversion between the MQTT "content type" field and Web PubSub messa
4545

4646
### Message content conversion
4747

48-
For text-based Web PubSub message data types, including `Text` and `Json`, they convert to and from MQTT by UTF-8 encoding. For binary-based Web PubSub message data types, including `Protobuf` and `Binary`, they remain exactly the same in the MQTT message content.
48+
For text-based Web PubSub message data types, including `text` and `json`, they convert to and from MQTT by UTF-8 encoding. For binary-based Web PubSub message data types, including `protobuf` and `binary`, they remain exactly the same in the MQTT message content.
4949

5050
### Message quality of service (QoS) conversion
5151

articles/backup/blob-restore.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Restore Azure Blobs
33
description: Learn how to restore Azure Blobs.
44
ms.topic: how-to
5-
ms.date: 12/24/2024
5+
ms.date: 04/14/2025
66
author: jyothisuri
77
ms.author: jsuri
88
---
@@ -97,14 +97,18 @@ To initiate a restore through the Azure Business Continuity Center, follow these
9797

9898
Consider the following example:
9999

100-
![Restore with prefix match](./media/blob-restore/prefix-match.png)
100+
![Screenshot shows the restore operation with prefix match.](./media/blob-restore/prefix-match.png)
101101

102102
The restore operation shown in the image performs the following actions:
103103

104104
- It restores the complete contents of *container1*.
105105
- It restores blobs in the lexicographical range *blob1* through *blob5* in *container2*. This range restores blobs with names such as *blob1*, *blob11*, *blob100*, *blob2*, and so on. Because the end of the range is exclusive, it restores blobs whose names begin with *blob4*, but doesn't restore blobs whose names begin with *blob5*.
106106
- It restores all blobs in *container3* and *container4*. Because the end of the range is exclusive, this range doesn't restore *container5*.
107107

108+
For **vaulted backup**, a prefix-match actively searches for items like folders and blobs under the specified container that start with the given input. For example, when you specify the prefix **b**, the blobs whose names begin with that letter are only replicated. Additionally, you can define a virtual directory and include up to **five prefixes**.
109+
110+
:::image type="content" source="./media/blob-restore/vaulted-backup-prefix-match.png" alt-text="Screenshot shows the option to restore with prefix match for vaulted backup." lightbox="./media/blob-restore/vaulted-backup-prefix-match.png":::
111+
108112
## Next steps
109113

110114
- [Overview of operational backup for Azure Blobs](blob-backup-overview.md)
63.4 KB
Loading

articles/communication-services/concepts/router/distribution-concepts.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,10 @@
22
title: Distribution mode concepts for Azure Communication Services
33
titleSuffix: An Azure Communication Services concept document
44
description: Learn about the Azure Communication Services Job Router distribution mode concepts.
5-
author: williamzhao
6-
manager: bgao
75
services: azure-communication-services
8-
9-
ms.author: williamzhao
6+
manager: chpalm
7+
ms.author: chpalm
8+
author: tophpalmer
109
ms.date: 05/06/2022
1110
ms.topic: conceptual
1211
ms.service: azure-communication-services

articles/communication-services/concepts/router/worker-capacity-concepts.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,10 @@
22
title: Worker capacity
33
titleSuffix: An Azure Communication Services concept document
44
description: Learn about the Azure Communication Services Job Router worker capacity concepts.
5-
author: williamzhao
6-
manager: bga
75
services: azure-communication-services
8-
9-
ms.author: williamzhao
6+
manager: chpalm
7+
ms.author: chpalm
8+
author: tophpalmer
109
ms.date: 06/08/2023
1110
ms.topic: conceptual
1211
ms.service: azure-communication-services

0 commit comments

Comments
 (0)