Skip to content

Commit 3c8b657

Browse files
Merge pull request #310626 from MicrosoftDocs/main
Auto Publish – main to live - 2026-01-19 06:00 UTC
2 parents 396bcde + ce4abbb commit 3c8b657

4 files changed

Lines changed: 16 additions & 6 deletions

File tree

articles/azure-vmware/self-service-maintenance-orchestration.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.custom: engagement-fy24
1010
# Customer intent: As a cloud administrator, I want to reschedule planned maintenance for my Azure VMware Solution, so that I can manage my resources effectively and minimize downtime during critical business periods.
1111
---
1212

13-
# Plan self-service maintenance for Azure VMware Solution (public preview)
13+
# Plan self-service maintenance for Azure VMware Solution
1414

1515
In this article, you learn about how to use the self-service maintenance orchestration feature to schedule or reschedule planned maintenance directly from the Azure portal. For more information, see [Host maintenance and lifecycle management](architecture-private-clouds.md).
1616

@@ -19,9 +19,10 @@ In this article, you learn about how to use the self-service maintenance orchest
1919
Before scheduling or rescheduling maintenance, ensure the following:
2020

2121
- An Azure VMware Solution private cloud in place.
22-
- A subscription with Early Access and Self Serve for Maintenance features enabled, available under Preview Features in the Azure portal.
22+
- Contributor Level access is required to view and edit the information on Maintenance blade.
2323

2424
## Schedule maintenance
25+
2526
To schedule maintenance, follow these steps:
2627

2728
1. Access the Maintenance pane by clicking the Schedule link in the banner. You see a list of upcoming maintenance events.
@@ -56,7 +57,9 @@ Once rescheduled, the system updates the schedule with the new date, visible in
5657
5758
## Errors and restrictions
5859
The following system error or warning messages appear while trying to reschedule maintenance tasks:
59-
- You can schedule/reschedule maintenance only before the upgrade deadline and on freeze days.
60+
- Each maintenance event has an internal deadline. You can schedule/reschedule maintenance only before the maintenance deadline. Dates beyond this appear greyed out on the portal. To reschedule past this point, raise a support ticket.
61+
62+
- Critical maintenance or fixes for critical security vulnerabilities may have the reschedule option disabled.
6063
- You can reschedule maintenance up to 24 hours before the start of the maintenance.
61-
- Each maintenance task has an internal deadline. Dates beyond this appear greyed out on the portal. To reschedule past this point, raise a support ticket. Critical maintenance or fixes for critical security vulnerabilities may have the reschedule option disabled.
64+
6265
- This feature is enabled only for specific maintenance activities. As a result, not all Azure VMware Solution maintenance tasks appear in this section or have the option to reschedule.

articles/container-apps/rule-based-routing.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -131,6 +131,13 @@ ROUTE_CONFIG_NAME="my-route-config"
131131
132132
This configuration defines two routing rules for HTTP traffic.
133133
134+
> [!NOTE]
135+
> The order of the routing rules matters.
136+
>
137+
> More specific prefixes need to be before less specific prefixes.
138+
>
139+
> For example, if the first rule matches the prefix /api, that will be used even if the second rule uses the prefix /api/v1.
140+
134141
| Property | Description |
135142
|---|---|
136143
| `description` | Human-readable label for the rule |

articles/expressroute/expressroute-introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Connectivity can be from an any-to-any (IP VPN) network, a point-to-point Ethern
3030
* Dynamic routing between your network and Microsoft via BGP.
3131
* Built-in redundancy in every peering location for higher reliability.
3232
* Connection uptime [SLA](https://azure.microsoft.com/support/legal/sla/).
33-
* QoS support for Skype for Business.
33+
* QoS support for Microsoft Teams.
3434

3535
For more information, see the [ExpressRoute FAQ](expressroute-faqs.md).
3636

articles/expressroute/metro.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ The following diagram allows for a comparison between the standard ExpressRoute
6666

6767
### Create an ExpressRoute Metro circuit
6868

69-
You can create an ExpressRoute Metro circuit in the Azure portal in any of the three metropolitan areas. Within the portal, specify one of the Metro peering locations and the corresponding service provider supported in that location. For more information, see [Create an ExpressRoute circuit](expressroute-howto-circuit-portal-resource-manager.md?pivots=expressroute-preview).
69+
You can create an ExpressRoute Metro circuit in the Azure portal in any of the metropolitan areas. Within the portal, specify one of the Metro peering locations and the corresponding service provider supported in that location. For more information, see [Create an ExpressRoute circuit](expressroute-howto-circuit-portal-resource-manager.md?pivots=expressroute-preview).
7070

7171
:::image type="content" source="./media/metro/create-metro-circuit.png" alt-text="Screenshot of creating an ExpressRoute Metro circuit.":::
7272

0 commit comments

Comments
 (0)