Merge pull request #270196 from SaibabaBalapur-MSFT/patch-118

prmerger-automator[bot] · web-flow · commit ca473e6e503e · 2024-06-13T17:33:15.000Z
(AzureCXP) fixes MicrosoftDocs/azure-docs#121050
diff --git a/articles/expressroute/expressroute-howto-routing-portal-resource-manager.md b/articles/expressroute/expressroute-howto-routing-portal-resource-manager.md
@@ -46,7 +46,7 @@ These instructions only apply to circuits created with service providers offerin
 This section helps you create, get, update, and delete the Microsoft peering configuration for an ExpressRoute circuit.
 
 > [!IMPORTANT]
-> Microsoft peering of ExpressRoute circuits that were configured prior to August 1, 2017 will have all service prefixes advertised through the Microsoft peering, even if route filters are not defined. Microsoft peering of ExpressRoute circuits that are configured on or after August 1, 2017 will not have any prefixes advertised until a route filter is attached to the circuit. For more information, see [Configure a route filter for Microsoft peering](how-to-routefilter-powershell.md).
+> Microsoft peering of ExpressRoute circuits that were configured prior to August 1, 2017 will have all Microsoft Office service prefixes advertised through the Microsoft peering, even if route filters are not defined. Microsoft peering of ExpressRoute circuits that are configured on or after August 1, 2017 will not have any prefixes advertised until a route filter is attached to the circuit. For more information, see [Configure a route filter for Microsoft peering](how-to-routefilter-powershell.md).
 > 
 > 
 

Original file line number	Diff line number	Diff line change
`@@ -46,7 +46,7 @@ These instructions only apply to circuits created with service providers offerin`
`46`	`46`	`This section helps you create, get, update, and delete the Microsoft peering configuration for an ExpressRoute circuit.`
`47`	`47`
`48`	`48`	`> [!IMPORTANT]`
`49`		`-> Microsoft peering of ExpressRoute circuits that were configured prior to August 1, 2017 will have all service prefixes advertised through the Microsoft peering, even if route filters are not defined. Microsoft peering of ExpressRoute circuits that are configured on or after August 1, 2017 will not have any prefixes advertised until a route filter is attached to the circuit. For more information, see [Configure a route filter for Microsoft peering](how-to-routefilter-powershell.md).`
	`49`	+> Microsoft peering of ExpressRoute circuits that were configured prior to August 1, 2017 will have all Microsoft Office service prefixes advertised through the Microsoft peering, even if route filters are not defined. Microsoft peering of ExpressRoute circuits that are configured on or after August 1, 2017 will not have any prefixes advertised until a route filter is attached to the circuit. For more information, see [Configure a route filter for Microsoft peering](how-to-routefilter-powershell.md).
`50`	`50`	`>`
`51`	`51`	`>`
`52`	`52`