You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/api-management/integrate-vnet-outbound.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ If you want to inject a Premium v2 (preview) API Management instance into a virt
48
48
49
49
### Network security group
50
50
51
-
A network security group must be associated with the subnet. Configure any network security group rules that you need for the gateway to access your API backends. To set up a network security group, see [Create a network security group](../virtual-network/manage-network-security-group.md).
51
+
A network security group must be associated with the subnet. Configure any network security group rules that you need for the gateway to access your API backends. Network security groups (NSG) can also be used to block outbound traffic to the internet and access only resources in your virtual network. To set up a network security group, see [Create a network security group](../virtual-network/manage-network-security-group.md).
Copy file name to clipboardExpand all lines: articles/application-gateway/configuration-http-settings.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,8 +16,8 @@ The Backend Settings enable you to manage the configurations for backend connect
16
16
## Types of Backend Settings in Application Gateway
17
17
While Portal users will only see the "Backend Settings" option, API users will have access to two types of settings. You must utilize the correct configuration, according to the protocol.
18
18
19
-
1. Backend HTTP settings - It is for Layer 7 proxy configurations that support HTTP, HTTPS, and WebSockets protocols.
20
-
2. Backend settings - It is for Layer 4 proxy (Preview) configurations that support TLS and TCP protocols.
19
+
* Backend HTTP settings - It is for Layer 7 proxy configurations that support HTTP, HTTPS, and WebSockets protocols.
20
+
* Backend settings - It is for Layer 4 proxy (Preview) configurations that support TLS and TCP protocols.
Copy file name to clipboardExpand all lines: articles/azure-maps/power-bi-visual-get-started.md
+31-2Lines changed: 31 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,12 +85,18 @@ Take the following steps to load the Azure Maps visual:
85
85
86
86
:::image type="content" source="media/power-bi-visual/bubble-layer-styled.png" alt-text="A screenshot of the Azure Maps visual displaying points as bubbles on the map with a custom style." lightbox="media/power-bi-visual/bubble-layer-styled.png":::
87
87
88
-
1. You can also show or hide labels in the **Format** pane. The following two images show maps with the **Show labels** setting turned on and off:
88
+
1. You can also show or hide labels in the **Format** pane. The following two images show maps with the **Labels** setting turned on and off:
89
89
90
90
:::image type="content" source="media/power-bi-visual/show-labels-on.png" alt-text="A screenshot of the Azure Maps visual displaying a map with the show labels setting turned on in the style section of the format pane in Power BI." lightbox="media/power-bi-visual/show-labels-on.png":::
91
91
92
92
:::image type="content" source="media/power-bi-visual/show-labels-off.png" alt-text="A screenshot of the Azure Maps visual displaying a map with the show labels setting turned off in the style section of the format pane in Power BI." lightbox="media/power-bi-visual/show-labels-off.png":::
93
93
94
+
1. You can also show or hide country borders, state or province borders, county borders, building, and road details in the **Format** pane. The following two images show maps with the **Country borders** settings turned on and off:
95
+
96
+
:::image type="content" source="media/power-bi-visual/country-borders-on.png" alt-text="A screenshot of the Azure Maps visual displaying a map with the country borders setting turned on in the style section of the format pane in Power BI." lightbox="media/power-bi-visual/country-borders-on.png":::
97
+
98
+
:::image type="content" source="media/power-bi-visual/country-borders-off.png" alt-text="A screenshot of the Azure Maps visual displaying a map with the country borders setting turned off in the style section of the format pane in Power BI." lightbox="media/power-bi-visual/country-borders-off.png":::
99
+
94
100
## Fields pane buckets
95
101
96
102
The following data buckets are available in the **Fields** pane of the Azure Maps visual.
@@ -117,7 +123,30 @@ The following settings are available in the **Style** section:
117
123
| Setting | Description |
118
124
|-------------|--------------|
119
125
| Style | The style of the map. The dropdown list contains [blank and blank accessible], [grayscale dark], [grayscale light], [high contrast dark], [high contrast light], [night], [road], [road shaded relief], [satellite] and [satellite road labels]. |
120
-
| Show labels | A toggle switch that enables you to either show or hide map labels. For more information, see list item number five in the previous section. |
126
+
| Labels | A toggle switch that allows you to show or hide map labels. For more information, see item number five in the previous section titled [Use the Azure Maps Power BI visual](#use-the-azure-maps-power-bi-visual). |
127
+
| Country borders | A toggle switch that controls the visibility of country borders. |
128
+
| State or province borders | A toggle switch that controls the visibility of the borders for the first-level administrative divisions, such as state or province borders. |
129
+
| County borders | A toggle switch that controls the visibility of the borders for the second-level administrative divisions, such as county borders. |
130
+
| Buildings | A toggle switch that controls the visibility of building footprints |
131
+
| Road details | A toggle switch that adjusts the level of detail for visible roads. Turning this off will reduce the number of roads shown on the map. |
132
+
133
+
The availability of the above toggles depends on the selected style. Below is a table showing the supported options for different styles:
134
+
135
+
| Map styles | Labels | Country borders | State or province borders | County borders | Buildings | Road details |
Copy file name to clipboardExpand all lines: articles/cost-management-billing/reservations/view-reservations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ If you're a billing administrator, use following steps to view and manage all re
36
36
1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to **Cost Management + Billing**.
37
37
- If you're an EA admin, in the left menu, select **Billing scopes** and then in the list of billing scopes, select one.
38
38
- If you're a Microsoft Customer Agreement billing profile owner, in the left menu, select **Billing profiles**. In the list of billing profiles, select one.
39
-
1. In the left menu, select **Products + services** > **Reservations**.
39
+
1. In the left menu, select **Products + services** > **Reservations + Hybrid Benefit**.
40
40
1. The complete list of reservations for your EA enrollment or billing profile is shown.
41
41
1. Billing administrators can take ownership of a reservation by selecting one or multiple reservations, selecting **Grant access** and selecting **Grant access** in the window that appears. For a Microsoft Customer Agreement, user should be in the same Microsoft Entra tenant (directory) as the reservation.
Copy file name to clipboardExpand all lines: articles/stream-analytics/run-job-in-virtual-network.md
+31-16Lines changed: 31 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: ahartoon
5
5
ms.author: anboisve
6
6
ms.service: azure-stream-analytics
7
7
ms.topic: how-to
8
-
ms.date: 02/05/2025
8
+
ms.date: 05/09/2025
9
9
ms.custom: references_regions, ignite-2024
10
10
---
11
11
@@ -19,11 +19,16 @@ Virtual network support enables you to lock down access to Azure Stream Analytic
19
19
-[Service endpoints](../virtual-network/virtual-network-service-endpoints-overview.md), which connect your data sources to your virtual network injected ASA job.
20
20
-[Service tags](../virtual-network/service-tags-overview.md), which allow or deny traffic to Azure Stream Analytics.
21
21
22
-
## Availability
23
-
Currently, this capability is only available in select **regions**: East US, East US 2, West US, West US 2, Central US, North-Central US, Central Canada, West Europe, North Europe, Southeast Asia, Brazil South, Japan East, UK South, Central India, Australia East, France Central, Germany West Central, and UAE North.
24
-
If you're interested in enabling virtual network integration in your region, **fill out this [form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbRzFwASREnlZFvs9gztPNuTdUMU5INk5VT05ETkRBTTdSMk9BQ0w3OEZDQi4u)**. Regions are added based on demand and feasibility. We will notify you if we are able to accommodate your request.
22
+
## Available Regions
23
+
Virtual network integration is currently supported in the following regions:
25
24
26
-
## Requirements for virtual network integration support
25
+
**East US, East US 2, West US, West US 2, Central US, North Central US, Central Canada, West Europe, North Europe, Southeast Asia, Brazil South, Japan East, UK South, Central India, Australia East, France Central, Germany West Central, and UAE North.**
26
+
27
+
If your region is not listed and you're interested in using this capability, please **fill out this [form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbRzFwASREnlZFvs9gztPNuTdUMU5INk5VT05ETkRBTTdSMk9BQ0w3OEZDQi4u)**.
28
+
29
+
We evaluate requests based on demand and feasibility, and will notify you if we are able to support your region.
30
+
31
+
## Prerequisites
27
32
28
33
- A **General purpose V2 (GPV2) Storage account** is required for virtual network injected ASA jobs.
29
34
- Virtual network injected ASA jobs require access to metadata such as checkpoints to be stored in Azure tables for operational purposes.
@@ -49,33 +54,43 @@ If you're interested in enabling virtual network integration in your region, **f
49
54
50
55
For more information about Azure NAT Gateway, see [Azure NAT Gateway](../nat-gateway/nat-overview.md).
51
56
52
-
## Subnet Requirements
57
+
- When configuring Azure IoT Hub with private endpoints, ensure that you also configure a private endpoint and corresponding DNS settings for the built-in Event Hubs-compatible endpoint. IoT Hub utilizes this endpoint to route messages, and without proper DNS resolution, services like Azure Stream Analytics may fail to connect.
58
+
- For guidance on setting up private endpoints and DNS for IoT Hub and Event Hubs, refer to the following resources:
59
+
60
+
-[IoT Hub support for virtual networks with Azure Private Link](../iot-hub/virtual-network-support.md)
61
+
-[Integrate Azure Event Hubs with Azure Private Link Service](../event-hubs/private-link-service.md)
62
+
-[Azure Private Endpoint DNS configuration](../private-link/private-endpoint-dns.md)
63
+
64
+
## Subnet Considerations
53
65
Virtual network integration depends on a dedicated subnet.
54
66
55
67
When configuring your delegated subnet, it is crucial to consider the IP range to accommodate both current and future requirements for your ASA workload. Since the subnet size cannot be modified once established, it is recommended to select a subnet size that can support the potential scale of your job. Additionally, be aware that Azure Networking reserves the first five IP addresses within the subnet range for internal use.
56
68
57
69
The scale operation affects the real, available supported instances for a given subnet size.
58
70
59
-
### Considerations for estimating IP ranges
71
+
**Considerations for estimating IP ranges**:
60
72
61
73
- Make sure the subnet range doesn't collide with ASA’s subnet range. Avoid IP range 10.0.0.0 to 10.0.255.255 as it's used by ASA.
62
74
- Reserve:
63
75
-**Five** IP addresses for Azure Networking
64
76
-**One** IP address is required to facilitate features such as sample data, test connection, and metadata discovery for jobs associated with this subnet.
65
77
-**Two** IP addresses are required for every six streaming unit (SU) or one SU V2 (ASA’s V2 pricing structure is launching July 1, 2023, see [here](https://aka.ms/AzureStreamAnalyticsisLaunchingaNewCompetitivePricingModel) for details)
66
78
67
-
### Releasing the subnet
68
-
When you indicate virtual network integration with your Azure Stream Analytics job, Azure portal automatically delegates the subnet to the ASA service. Azure undelegates the subnet in the following scenarios:
79
+
**Subnet Delegation and Release Behavior**:
80
+
81
+
- When you enable virtual network integration for an Azure Stream Analytics (ASA) job, the Azure portal automatically delegates the specified subnet to the ASA service.
82
+
83
+
- ASA will automatically undelegate the subnet in either of the following cases:
84
+
- You disable virtual network integration for the last ASA job using that subnet via the Azure portal.
85
+
- You delete the last ASA job associated with the subnet.
86
+
87
+
Note: Multiple ASA jobs can share the same subnet. The "last job" refers to the point when no other ASA jobs are using that subnet. Once the last job is removed, ASA releases the delegated subnet. This may take a few minutes to complete.
69
88
70
-
- You inform us that virtual network integration is no longer needed for the [last job](#last-job) associated with specified subnet via the ASA portal (see the how-to section).
71
-
- You delete the [last job](#last-job) associated with the specified subnet.
89
+
**Subnet Must Allow Intra-Subnet Traffic**:
72
90
73
-
### Intra-Subnet traffic
74
-
The subnet configuration must enable intra-subnet network traffic. This means that it must allow inbound and outbound traffic where both the source and destination IP addresses reside within the same subnet.
75
-
Learn more [here](../virtual-network/network-security-group-how-it-works.md#intra-subnet-traffic).
91
+
- The subnet configuration must enable intra-subnet network traffic.
92
+
- This means that it must allow inbound and outbound traffic where both the source and destination IP addresses reside within the same subnet. Learn more [here](../virtual-network/network-security-group-how-it-works.md#intra-subnet-traffic).
76
93
77
-
### Last job
78
-
Several Stream Analytics jobs can utilize the same subnet. The last job here refers to no other jobs utilizing the specified subnet. When the last job has been deleted or removed by associated, Azure Stream Analytics releases the subnet as a resource, which was delegated to ASA as a service. Allow several minutes for this action to be completed.
0 commit comments