Merge pull request #291094 from MicrosoftDocs/main

11/26/2024 AM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -3749,6 +3749,21 @@
       "source_path_from_root": "/articles/virtual-network/tutorial-connect-virtual-networks-cli.md",
       "redirect_url": "/azure/virtual-network/tutorial-connect-virtual-networks",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/virtual-network/ip-services/public-ip-upgrade-portal.md",
+      "redirect_url": "/azure/virtual-network/ip-services/public-ip-upgrade",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/virtual-network/ip-services/public-ip-upgrade-cli.md",
+      "redirect_url": "/azure/virtual-network/ip-services/public-ip-upgrade",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/virtual-network/ip-services/public-ip-upgrade-powershell.md",
+      "redirect_url": "/azure/virtual-network/ip-services/public-ip-upgrade",
+      "redirect_document_id": false
     }
   ]
 }

articles/app-service/environment/app-service-app-service-environment-network-architecture-overview.md

@@ -61,27 +61,10 @@ If the endpoint being called is **inside** of the virtual network topology, the
 
 However, since an App Service Environment is always located within a subnet, you're guaranteed that the internal IP address of a compute resource running an app will always lie within the CIDR range of the subnet.  As a result, when fine-grained ACLs or network security groups are used to secure access to other endpoints within the virtual network, the subnet range containing the App Service Environment needs to be granted access.
 
-The following diagram shows these concepts in more detail:
-
-![Outbound Network Addresses][OutboundNetworkAddresses]
-
-In the above diagram:
-
-* Since the public VIP of the App Service Environment is 192.23.1.2, that is the outbound IP address used when making calls to "Internet" endpoints.
-* The CIDR range of the containing subnet for the App Service Environment is 10.0.1.0/26.  Other endpoints within the same virtual network infrastructure will see calls from apps as originating from somewhere within this address range.
-
 ## Calls Between App Service Environments
 
 A more complex scenario can occur if you deploy multiple App Service Environments in the same virtual network, and make outbound calls from one App Service Environment to another App Service Environment.  These types of cross App Service Environment calls will also be treated as "Internet" calls.
 
-The following diagram shows an example of a layered architecture with apps on one App Service Environment (for example "Front door" web apps) calling apps on a second App Service Environment (for example internal back-end API apps not intended to be accessible from the Internet).
-
-![Calls Between App Service Environments][CallsBetweenAppServiceEnvironments]
-
-In the example above the App Service Environment "ASE One" has an outbound IP address of 192.23.1.2.  If an app running on this App Service Environment makes an outbound call to an app running on a second App Service Environment ("ASE Two") located in the same virtual network, the outbound call will be treated as an "Internet" call.  As a result the network traffic arriving on the second App Service Environment will show as originating from 192.23.1.2 (that is, not the subnet address range of the first App Service Environment).
-
-Even though calls between different App Service Environments are treated as "Internet" calls, when both App Service Environments are located in the same Azure region the network traffic will remain on the regional Azure network and won't physically flow over the public Internet.  As a result you can use a network security group on the subnet of the second App Service Environment to only allow inbound calls from the first App Service Environment (whose outbound IP address is 192.23.1.2), thus ensuring secure communication between the App Service Environments.
-
 ## Additional Links and Information
 
 Details on inbound ports used by App Service Environments and using network security groups to control inbound traffic is available [here][controllinginboundtraffic].
@@ -96,5 +79,3 @@ Details on using user-defined routes to grant outbound Internet access to App Se
 <!-- IMAGES -->
 [GeneralNetworkFlows]: ./media/app-service-app-service-environment-network-architecture-overview/NetworkOverview-1.png
 [OutboundIPAddress]: ./media/app-service-app-service-environment-network-architecture-overview/OutboundIPAddress-1.png
-[OutboundNetworkAddresses]: ./media/app-service-app-service-environment-network-architecture-overview/OutboundNetworkAddresses-1.png
-[CallsBetweenAppServiceEnvironments]: ./media/app-service-app-service-environment-network-architecture-overview/CallsBetweenEnvironments-1.png

articles/app-service/environment/media/app-service-app-service-environment-network-architecture-overview/CallsBetweenEnvironments-1.png

@@ -219,8 +219,6 @@ To create the same routes manually, follow these steps:
 
 5. After you create the new route table, go to the subnet. Select your route table from the list in the portal. After you save the change, you should then see the NSGs and routes noted with your subnet.
 
-    ![Screenshot that shows NSGs and routes.][7]
-
 ## Service endpoints
 
 Service endpoints enable you to restrict access to multi-tenant services to a set of Azure virtual networks and subnets. For more information, see [Virtual Network service endpoints][serviceendpoints].
@@ -235,7 +233,6 @@ When service endpoints are enabled on a subnet with an instance of Azure SQL, al
 [1]: ./media/network_considerations_with_an_app_service_environment/networkase-overflow.png
 [2]: ./media/network_considerations_with_an_app_service_environment/networkase-overflow2.png
 [6]: ./media/network_considerations_with_an_app_service_environment/networkase-udr.png
-[7]: ./media/network_considerations_with_an_app_service_environment/networkase-subnet.png
 [8]: ./media/network_considerations_with_an_app_service_environment/serviceendpoint.png
 
 <!--Links-->

articles/app-service/environment/media/app-service-app-service-environment-network-architecture-overview/OutboundNetworkAddresses-1.png

@@ -57,8 +57,8 @@ You can use rewrite conditions to evaluate the content of HTTP(S) requests and r
 
   An action can have the following value types or their combinations:
   * Text.
-  * Request header's value - To use a captured request header value, specify the syntax as `{http_req_headerName}`.
-  * Response header's value - To use a captured response header value from the preceding Condition, specify the syntax as `{http_resp_headerName}`. You can use `{capt_header_value_matcher}` when the value is captured from Action Set's "Set-Cookie" response header. Know more about [capture under Action set](#syntax-for-capturing).
+  * Request header's value - To use a captured Request header's value, specify the syntax as `{http_req_headerName}`.
+  * Response header's value - To use a captured Response header's value from the preceding Condition, specify the syntax as `{http_resp_headerName}`. The Rewrite Action block also supports the "Header Value Matcher" field for Set-Cookie header. This optional field lets you match as well as capture the value of a specific header when multiple Set-Cookie headers with the same name exist. To manipulate that specific cookie's captured value, you can then use `{capt_header_value_matcher}`. Know more about [capture under Action set](#syntax-for-capturing).
   * Server variable - To use a server variable, specify the syntax as `{var_serverVariable}`. [List of supported Server variables](#server-variables).
 
 > [!Note]

articles/app-service/environment/media/network_considerations_with_an_app_service_environment/networkase-subnet.png

@@ -25,46 +25,17 @@ Initially all bubbles have the same fill color. If a field is passed into the **
 | Shape          | Transparency. The fill transparency of each bubble. |
 | Color          | Fill color of each bubble. This option is hidden when a field is passed into the **Legend** bucket of the **Fields** pane and a separate **Data colors** section appears in the **Format** pane. |
 | Border         | Settings for the border include color, width, transparency and blur.<br/>&nbsp;&nbsp;&nbsp;&nbsp;• Color specifies the color that outlines the bubble. This option is hidden when the **High-contrast outline** option is enabled.<br/>&nbsp;&nbsp;&nbsp;&nbsp;• Width specifies the width of the outline in pixels.<br/>&nbsp;&nbsp;&nbsp;&nbsp;• Transparency specifies the transparency of each bubble.<br/>&nbsp;&nbsp;&nbsp;&nbsp;• Blur specifies the amount of blur applied to the outline of the bubble. A value of one blurs the bubbles such that only the center point has no transparency. A value of 0 apply any blur effect.|
-| Zoom           | Settings for the zoom property include scale, maximum and minimum.<br/>&nbsp;&nbsp;&nbsp;&nbsp;• (Deprecated) Zoom scale is the amount the bubbles should scale relative to the zoom level. A zoom scale of one means no scaling. Large values make bubbles smaller when zoomed out and larger when zoomed in. This helps to reduce the clutter on the map when zoomed out, yet ensures points stand out more when zoomed in. A value of 1 doesn't apply any scaling.<br/>&nbsp;&nbsp;&nbsp;&nbsp;• Maximum zoom level tiles are available.<br/>&nbsp;&nbsp;&nbsp;&nbsp;• Minimum zoom level tiles are available.     |
+| Zoom           | Settings for the zoom property include scale, maximum and minimum.<br/>&nbsp;&nbsp;&nbsp;&nbsp;• Maximum zoom level tiles are available.<br/>&nbsp;&nbsp;&nbsp;&nbsp;• Minimum zoom level tiles are available.     |
 | Options        | Settings for the options property include pitch alignment and layer position.<br/>&nbsp;&nbsp;&nbsp;&nbsp;• Pitch alignment specifies how the bubbles look when the map is pitched.<br/>&nbsp;&nbsp;&nbsp;&nbsp;• layer position specifies the position of the layer relative to other map layers.   |
 
 ## Bubble size scaling
 
-> [!NOTE]
->
-> **Bubble size scaling retirement**
->
-> The Power BI Visual bubble layer **Bubble size scaling** settings were deprecated starting in the September 2023 release of Power BI. You can no longer create reports using these settings, but existing reports will continue to work. It is recomended that you upgrade existing reports that use these settings to the new **range scaling** property. To upgrade to the new **range scaling** property, select the desired option in the **Range scaling** drop-down list:
->
-> :::image type="content" source="./media/power-bi-visual/range-scaling-drop-down.png" alt-text="A screenshot of the range scaling drop-down":::
->
-> For more information on the range scaling settings, see **range scaling** in the [previous section](#add-a-bubble-layer).
-
-If a field is passed into the **Size** bucket of the **Fields** pane, the bubbles are scaled relatively to the measure value of each data point. The **Size** option in the **Bubble layer** section of the **Format** pane disappears when a field is passed into the **Size** bucket, as the bubbles have their radii scaled between a min and max value. The following options appear in the **Bubble layer** section of the **Format** pane when a **Size** bucket has a field specified.
+If a field is passed into the **Size** bucket of the **Fields** pane, the bubbles are scaled relatively to the measure value of each data point. The **Size** option in the **Bubble layer** section of the **Format** pane disappears when a field is passed into the **Size** bucket, as the bubbles have their radius scaled between a min and max value. The following options appear in the **Bubble layer** section of the **Format** pane when a **Size** bucket has a field specified.
 
 | Setting             | Description  |
 |---------------------|--------------|
 | Min size            | Minimum bubble size when scaling the data.|
 | Max size            | Maximum bubble size when scaling the data.|
-| Size scaling method | Scaling algorithm used to determine relative bubble size.<br/><br/>&nbsp;• Linear: Range of input data linearly mapped to the min and max size. (default)<br/>&nbsp;• Log: Range of input data logarithmically mapped to the min and max size.<br/>&nbsp;• Cubic-Bezier: Specify X1, Y1, X2, Y2 values of a Cubic-Bezier curve to create a custom scaling method. |
-
-When the **Size scaling method** is set to **Log**, the following options are made available.
-
-| Setting   | Description      |
-|-----------|------------------|
-| Log scale | The logarithmic scale to apply when calculating the size of the bubbles. |
-
-When the **Size scaling method** is set to **Cubic-Bezier**, the following options are made available to customize the scaling curve.
-
-| Setting | Description                           |
-|---------|---------------------------------------|
-| X1      | X1 parameter of a cubic Bezier curve. |
-| Y1      | X2 parameter of a cubic Bezier curve. |
-| X2      | Y1 parameter of a cubic Bezier curve. |
-| Y2      | Y2 parameter of a cubic Bezier curve. |
-
-> [!TIP]
-> [https://cubic-bezier.com/](https://cubic-bezier.com/) has a handy tool for creating the parameters for Cubic-Bezier curves.
 
 ## Category labels
 

articles/app-service/environment/network-info.md

@@ -85,21 +85,9 @@ The general layer section of the **Format** pane are common settings that apply
 | Setting        | Description                            |
 |----------------|----------------------------------------|
 | Unselected transparency | The transparency of shapes that aren't selected, when one or more shapes are selected.  |
-| Show zeros     | (Deprecated) Specifies if points that have a size value of zero should be shown on the map using the minimum radius. |
-| Show negatives | (Deprecated) Specifies if absolute value of negative size values should be plotted.   |
 | Min data value | The minimum value of the input data to scale against. Good for clipping outliers.  |
 | Max data value | The maximum value of the input data to scale against. Good for clipping outliers.  |
 
-> [!NOTE]
->
-> **General layer settings retirement**
->
-> The **Show zeros** and **Show negatives** Power BI Visual General layer settings were deprecated starting in the September 2023 release of Power BI. You can no longer create new reports using these settings, but existing reports will continue to work. It is recommended that you upgrade existing reports. To upgrade to the new **range scaling** property, select the desired option in the **Range scaling** drop-down list:
->
-> :::image type="content" source="./media/power-bi-visual/range-scaling-drop-down.png" alt-text="A screenshot of the range scaling drop-down":::
->
-> For more information on the range scaling option, see **Range scaling** in the properties table of the [Add a bubble layer] article.
-
 ## Next steps
 
 Change how your data is displayed on the map: