Skip to content

Commit 27a95a7

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into sfi-remediation-adhoc
2 parents cb3df4a + 4c2a564 commit 27a95a7

File tree

7 files changed

+45
-45
lines changed

7 files changed

+45
-45
lines changed

articles/cloud-shell/vnet/overview.md

Lines changed: 17 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
description: This article describes a scenario for using Azure Cloud Shell in a private virtual network.
3-
ms.contributor: jahelmic
4-
ms.date: 04/22/2024
3+
ms.date: 10/23/2024
54
ms.topic: conceptual
65
title: Use Cloud Shell in an Azure virtual network
76
---
@@ -12,7 +11,7 @@ By default, Azure Cloud Shell sessions run in a container in a Microsoft network
1211
from your resources. Commands that run inside the container can't access resources in a private
1312
virtual network. For example, you can't use Secure Shell (SSH) to connect from Cloud Shell to a
1413
virtual machine that has only a private IP address, or use `kubectl` to connect to a Kubernetes
15-
cluster that has locked down access.
14+
cluster with locked-down access.
1615

1716
To provide access to your private resources, you can deploy Cloud Shell into an Azure virtual
1817
network that you control. This technique is called _virtual network isolation_.
@@ -29,15 +28,15 @@ Deploying Cloud Shell in a private virtual network offers these benefits:
2928
## Things to consider before deploying Azure Cloud Shell in a virtual network
3029

3130
- Starting Cloud Shell in a virtual network is typically slower than a standard Cloud Shell session.
32-
- Virtual network isolation requires you to use [Azure Relay][01], which is a paid service. In the
31+
- Virtual network isolation requires you to use [Azure Relay][02], which is a paid service. In the
3332
Cloud Shell scenario, one hybrid connection is used for each administrator while they're using
3433
Cloud Shell. The connection is automatically closed when the Cloud Shell session ends.
3534

3635
## Architecture
3736

3837
The following diagram shows the resource architecture that you must build to enable this scenario.
3938

40-
![Illustration of a Cloud Shell isolated virtual network architecture.][03]
39+
![Illustration of a Cloud Shell isolated virtual network architecture.][04]
4140

4241
- **Customer client network**: Client users can be located anywhere on the internet to securely
4342
access and authenticate to the Azure portal and use Cloud Shell to manage resources contained in
@@ -48,20 +47,26 @@ The following diagram shows the resource architecture that you must build to ena
4847
- **Customer virtual network**: This is the network that contains the subnets to support virtual
4948
network isolation. Resources such as virtual machines and services are directly accessible from
5049
Cloud Shell without the need to assign a public IP address.
51-
- **Azure Relay**: [Azure Relay][01] allows two endpoints that aren't directly reachable to
50+
- **Azure Relay**: [Azure Relay][02] allows two endpoints that aren't directly reachable to
5251
communicate. In this case, it's used to allow the administrator's browser to communicate with the
5352
container in the private network.
5453
- **File share**: Cloud Shell requires a storage account that's accessible from the virtual network.
5554
The storage account provides the file share used by Cloud Shell users.
5655

57-
## Related links
56+
## Pricing
5857

5958
Cloud Shell requires a new or existing Azure Files share to be mounted to persist files across
60-
sessions. Storage incurs regular costs. If you have deployed Azure Cloud Shell in a private virtual
59+
sessions. Storage incurs regular costs. When you deploy Azure Cloud Shell in a private virtual
6160
network, you pay for network resources. For pricing information, see
62-
[Pricing of Azure Cloud Shell][02].
61+
[Pricing of Azure Cloud Shell][01].
62+
63+
## Next steps
64+
65+
When you're ready to deploy your own instance of Cloud Shell, see
66+
[Deploy Azure Cloud Shell in a virtual network with quickstart templates][03].
6367

6468
<!-- link references -->
65-
[01]: /azure/azure-relay/relay-what-is-it
66-
[02]: ../pricing.md
67-
[03]: media/overview/data-diagram.png
69+
[01]: ../pricing.md
70+
[02]: /azure/azure-relay/relay-what-is-it
71+
[03]: deployment.md
72+
[04]: media/overview/data-diagram.png

articles/cloud-shell/vnet/troubleshooting.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ description: >
33
This article provides instructions for troubleshooting a private virtual network deployment of
44
Azure Cloud Shell.
55
ms.contributor: jahelmic
6-
ms.date: 10/26/2023
6+
ms.date: 10/23/2024
77
ms.topic: troubleshooting
88
title: Troubleshoot Azure Cloud Shell in a private virtual network
99
---
@@ -13,7 +13,7 @@ This article provides instructions for troubleshooting a private virtual network
1313
Cloud Shell. For best results, and to be supportable, following the deployment instructions in the
1414
[Deploy Azure Cloud Shell in a virtual network using quickstart templates][03] article.
1515

16-
## Verify you have set the correct permissions
16+
## Verify you have the correct permissions
1717

1818
To configure Azure Cloud Shell in a virtual network, you must have the **Owner** role assignment on
1919
the subscription. To view and assign roles, see [List owners of a subscription][01].
@@ -79,28 +79,13 @@ permissions for your subscription:
7979

8080
[![Screenshot showing the network relay role assignments.][ss04a]][ss04x]
8181

82-
## Redeploy Cloud Shell for a private virtual network
82+
## When all else fails
8383

8484
Verify the configurations described in this article. If you continue receive an error message when
8585
you try to use your deployment of Cloud Shell, you have two options:
8686

87-
1. Open a support ticket
8887
1. Redeploy Cloud Shell for a private virtual network
89-
90-
### Open a support ticket
91-
92-
If you want to open a support ticket, you can do so from the Azure portal. Be sure to capture any
93-
error messages, including the **Correlation Id** and **Activity Id** values. Don't change any
94-
settings or delete any resources until instructed to by a support technician.
95-
96-
Follow these steps to open a support ticket:
97-
98-
1. Select the **Support & Troubleshooting** icon on the top navigation bar in the Azure portal.
99-
1. From the **Support & Troubleshooting** pane, select **Help + support**.
100-
1. Select **Create a support request** at the top of the center pane.
101-
1. Follow the instructions to create a support ticket.
102-
103-
[![Screenshot of creating a support ticket in the Azure portal.][ss05a]][ss05x]
88+
1. Open a support ticket
10489

10590
### Redeploy Cloud Shell for a private virtual network
10691

@@ -124,13 +109,28 @@ The following list provides a description of the resources created by the deploy
124109
- A **Relay** resource with the name of the relay namespace you provided in the deployment template.
125110
- A **Storage account** resource with the name you provided in the deployment template.
126111

127-
Once you have removed the resources, you can redeploy Cloud Shell by following the steps in the
112+
After you remove the resources, you can redeploy Cloud Shell by following the steps in the
128113
[Deploy Azure Cloud Shell in a virtual network using quickstart templates][03] article.
129114

130115
You can find these resources by viewing the resource group in the Azure portal.
131116

132117
[![Screenshot of resources created by the deployment.][ss02a]][ss02x]
133118

119+
### Open a support ticket
120+
121+
If you want to open a support ticket, you can do so from the Azure portal. Be sure to capture any
122+
error messages, including the **Correlation Id** and **Activity Id** values. Don't change any
123+
settings or delete any resources until instructed to by a support technician.
124+
125+
Follow these steps to open a support ticket:
126+
127+
1. Select the **Support & Troubleshooting** icon on the top navigation bar in the Azure portal.
128+
1. From the **Support & Troubleshooting** pane, select **Help + support**.
129+
1. Select **Create a support request** at the top of the center pane.
130+
1. Follow the instructions to create a support ticket.
131+
132+
[![Screenshot of creating a support ticket in the Azure portal.][ss05a]][ss05x]
133+
134134
<!-- link references -->
135135
[01]: /azure/role-based-access-control/role-assignments-list-portal#list-owners-of-a-subscription
136136
[02]: https://portal.azure.com/

articles/internet-peering/faqs.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,13 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: internet-peering
88
ms.topic: faq
9-
ms.date: 09/20/2023
9+
ms.date: 10/23/2024
1010
---
1111

1212
# Internet peering frequently asked questions (FAQ)
1313

14+
This article provides answers to some of the frequently asked questions about Internet peering.
15+
1416
## General
1517

1618
### What is the difference between Internet peering and Peering Service?
@@ -54,4 +56,3 @@ Carriers that offer SLA and enterprise-grade internet are doing so on their part
5456
### If a service provider already peers with Microsoft, what kind of changes are required to support Peering Service?
5557

5658
Peering Service partners must have an Azure subscription and manage the Peering Service connections using the Azure portal as this is where customer prefixes are registered, performance metrics are viewed, and support tickets are logged, among other features. If a provider has existing peering with Microsoft but no Azure subscription, the resources must be added to your subscription before you're able to convert these to the Peering Service configuration. During the configuration change, Microsoft changes the policy group during a hard restart of the BGP session. No configuration changes are required on the partner’s side, unless the telco partner is supporting Peering Service for voice, then BFD configuration is required. For more information, see [Azure Internet peering for Communications Services walkthrough](walkthrough-communications-services-partner.md).
57-

articles/internet-peering/peering-service-partner-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: halkazwini
55
ms.author: halkazwini
66
ms.service: internet-peering
77
ms.topic: concept-article
8-
ms.date: 08/18/2023
8+
ms.date: 10/23/2024
99
---
1010

1111
# Azure Peering Service partner overview
@@ -47,7 +47,7 @@ In addition, Peering Service partners are able to see received routes reported i
4747

4848
:::image type="content" source="./media/peering-service-partner-overview/peering-service-partner-latency-report.png" alt-text="Diagram showing monitoring platform for Peering Service.":::
4949

50-
## Next steps
50+
## Related content
5151

5252
- To establish a Direct interconnect for Peering Service, see [Internet peering for Peering Service walkthrough](walkthrough-peering-service-all.md).
5353
- To establish a Direct interconnect for Peering Service Voice, see [Internet peering for Peering Service Voice walkthrough](walkthrough-communications-services-partner.md).

articles/network-watcher/network-watcher-visualize-nsg-flow-logs-open-source-tools.md

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: halkazwini
66
ms.author: halkazwini
77
ms.service: azure-network-watcher
88
ms.topic: how-to
9-
ms.date: 09/26/2024
9+
ms.date: 10/23/2024
1010
---
1111

1212
# Visualize Azure Network Watcher NSG flow logs using open source tools
@@ -235,19 +235,15 @@ The sample dashboard provides several visualizations of the flow logs:
235235
236236
5. Top 10 Source/Destination IPs – bar charts showing the top 10 source and destination IPs. You can adjust these charts to show more or less top IPs. From here, you can see the most commonly occurring IPs and the traffic decision (allow or deny) being made towards each IP.
237237
238-
![Screenshot shows a sample dashboard with flows by top ten source and destination I P addresses.][6]
239-
240-
6. Flow Tuples – this table shows you the information contained within each flow tuple, and its corresponding NGS and rule.
241-
242-
![Screenshot shows flow tuples in a table.][7]
238+
6. Flow Tuples – a table showing the information contained within each flow tuple, and its corresponding NGS and rule.
243239
244240
Using the query bar at the top of the dashboard, you can filter down the dashboard based on any parameter of the flows, such as subscription ID, resource groups, rule, or any other variable of interest. For more about Kibana's queries and filters, see the [official documentation](https://www.elastic.co/guide/en/beats/packetbeat/current/kibana-queries-filters.html)
245241
246242
## Conclusion
247243
248244
By combining the network security group flow logs with the Elastic Stack, we have come up with powerful and customizable way to visualize our network traffic. These dashboards allow you to quickly gain and share insights about your network traffic, and filter down and investigate on any potential anomalies. Using Kibana, you can tailor these dashboards and create specific visualizations to meet any security, audit, and compliance needs.
249245
250-
## Next steps
246+
## Next step
251247
252248
Learn how to visualize your NSG flow logs with Power BI by visiting [Visualize NSG flows logs with Power BI](network-watcher-visualize-nsg-flow-logs-power-bi.md)
253249
@@ -259,5 +255,3 @@ Learn how to visualize your NSG flow logs with Power BI by visiting [Visualize N
259255
[3]: ./media/network-watcher-visualize-nsg-flow-logs-open-source-tools/figure3.png
260256
[4]: ./media/network-watcher-visualize-nsg-flow-logs-open-source-tools/figure4.png
261257
[5]: ./media/network-watcher-visualize-nsg-flow-logs-open-source-tools/figure5.png
262-
[6]: ./media/network-watcher-visualize-nsg-flow-logs-open-source-tools/figure6.png
263-
[7]: ./media/network-watcher-visualize-nsg-flow-logs-open-source-tools/figure7.png

0 commit comments

Comments
 (0)