Skip to content

Commit 6273f09

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents bbeeb57 + ac85194 commit 6273f09

File tree

151 files changed

+4110
-235
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

151 files changed

+4110
-235
lines changed

articles/azure-resource-manager/management/manage-resource-groups-cli.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.author: jgao
88
ms.custom: devx-track-azurecli
99
---
1010

11-
# Manage Azure Resource Manager resource groups by using Azure CLI
11+
# Manage Azure Resource Groups by using Azure CLI
1212

1313
Learn how to use Azure CLI with [Azure Resource Manager](overview.md) to manage your Azure resource groups. For managing Azure resources, see [Manage Azure resources by using Azure CLI](manage-resources-cli.md).
1414

@@ -114,4 +114,4 @@ To manage access to a resource group, use [Azure role-based access control (Azur
114114
## Next steps
115115

116116
- To learn Azure Resource Manager, see [Azure Resource Manager overview](overview.md).
117-
- To learn the Resource Manager template syntax, see [Understand the structure and syntax of Azure Resource Manager templates](../templates/syntax.md).
117+
- To learn the Resource Manager template syntax, see [Understand the structure and syntax of Azure Resource Manager templates](../templates/syntax.md).

articles/azure-resource-manager/management/manage-resource-groups-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.author: jgao
88
ms.custom: devx-track-azurepowershell
99

1010
---
11-
# Manage Azure Resource Manager resource groups by using Azure PowerShell
11+
# Manage Azure Resource Groups by using Azure PowerShell
1212

1313
Learn how to use Azure PowerShell with [Azure Resource Manager](overview.md) to manage your Azure resource groups. For managing Azure resources, see [Manage Azure resources by using Azure PowerShell](manage-resources-powershell.md).
1414

articles/data-factory/tutorial-managed-virtual-network-on-premise-sql-server.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -212,15 +212,11 @@ the page.
212212

213213
## Creating Forwarding Rule to Endpoint
214214

215-
1. Login and download the port forwarding script [ip_fwd.sh](https://github.com/sajitsasi/az-ip-fwd/blob/main/ip_fwd.sh) to your backend server VMs.
215+
1. Login and copy script [ip_fwd.sh](https://github.com/sajitsasi/az-ip-fwd/blob/main/ip_fwd.sh) to your backend server VMs.
216216
2. Run the script on with the following options:<br/>
217-
**sudo chmod +x ip_fwd.sh**<br/>
218217
**sudo ./ip_fwd.sh -i eth0 -f 1433 -a <FQDN/IP> -b 1433**<br/>
219218
<FQDN/IP> is your target SQL Server IP.<br/>
220219

221-
> [!Note]
222-
> The above script runs only once. In order to ensure that that port forwarding is enabled every time the machine starts, it should be configured as a startup service.
223-
224220
> [!Note]
225221
> FQDN doesn't work for on-premises SQL Server unless you add a record in Azure DNS zone.
226222
@@ -269,6 +265,9 @@ data factory from the resources list.
269265

270266
:::image type="content" source="./media/tutorial-managed-virtual-network/linked-service-3.png" alt-text="Screenshot that shows the SQL server linked service creation page.":::
271267

268+
> [!Note]
269+
> If you have more than one SQL Server and need to define multiple load balancer rules and IP table records with different ports, make sure you explicitly add the port name after the FQDN when you edit Linked Service. The NAT VM will handle the port translation. If it's not explicitly specified, the connection will always time-out.
270+
272271
## Troubleshooting
273272

274273
Go to the backend server VM, confirm telnet the SQL Server works: **telnet **<**FQDN**>** 1433**.

articles/defender-for-cloud/alerts-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -258,7 +258,7 @@ At the bottom of this page, there's a table describing the Microsoft Defender fo
258258
| **An IP that connected to your Azure App Service FTP Interface was found in Threat Intelligence**<br>(AppServices_IncomingTiClientIpFtp) | Azure App Service FTP log indicates a connection from a source address that was found in the threat intelligence feed. During this connection, a user accessed the pages listed.<br>(Applies to: App Service on Windows and App Service on Linux) | Initial Access | Medium |
259259
| **Attempt to run high privilege command detected**<br>(AppServices_HighPrivilegeCommand) | Analysis of App Service processes detected an attempt to run a command that requires high privileges.<br>The command ran in the web application context. While this behavior can be legitimate, in web applications this behavior is also observed in malicious activities.<br>(Applies to: App Service on Windows) | - | Medium |
260260
| **Communication with suspicious domain identified by threat intelligence**<br>(AzureDNS_ThreatIntelSuspectDomain) | Communication with suspicious domain was detected by analyzing DNS transactions from your resource and comparing against known malicious domains identified by threat intelligence feeds. Communication to malicious domains is frequently performed by attackers and could imply that your resource is compromised. | Initial Access, Persistence, Execution, Command And Control, Exploitation | Medium |
261-
| **Connection to web page from anomalous IP address detected**<br>(AppServices_AnomalousPageAccess) | Azure App Service activity log indicates an anomalous connection to a sensitive web page from the listed source IP address. This might indicate that someone is attempting a brute force attack into your web app administration pages. It might also be the result of a new IP address being used by a legitimate user. If the source IP address is trusted, you can safely suppress this alert for this resource. To learn how to suppress security alerts, see [Suppress alerts from Microsoft Defender for Cloud](alerts-suppression-rules.md). <br>(Applies to: App Service on Windows and App Service on Linux) | Initial Access | Medium |
261+
| **Connection to web page from anomalous IP address detected**<br>(AppServices_AnomalousPageAccess) | Azure App Service activity log indicates an anomalous connection to a sensitive web page from the listed source IP address. This might indicate that someone is attempting a brute force attack into your web app administration pages. It might also be the result of a new IP address being used by a legitimate user. If the source IP address is trusted, you can safely suppress this alert for this resource. To learn how to suppress security alerts, see [Suppress alerts from Microsoft Defender for Cloud](alerts-suppression-rules.md). <br>(Applies to: App Service on Windows and App Service on Linux) | Initial Access | Low |
262262
| **Dangling DNS record for an App Service resource detected**<br>(AppServices_DanglingDomain) | A DNS record that points to a recently deleted App Service resource (also known as "dangling DNS" entry) has been detected. This leaves you susceptible to a subdomain takeover. Subdomain takeovers enable malicious actors to redirect traffic intended for an organization’s domain to a site performing malicious activity.<br>(Applies to: App Service on Windows and App Service on Linux) | - | High |
263263
| **Detected encoded executable in command line data**<br>(AppServices_Base64EncodedExecutableInCommandLineParams) | Analysis of host data on {Compromised host} detected a base-64 encoded executable. This has previously been associated with attackers attempting to construct executables on-the-fly through a sequence of commands, and attempting to evade intrusion detection systems by ensuring that no individual command would trigger an alert. This could be legitimate activity, or an indication of a compromised host.<br>(Applies to: App Service on Windows) | Defense Evasion, Execution | High |
264264
| **Detected file download from a known malicious source**<br>(AppServices_SuspectDownload) | Analysis of host data has detected the download of a file from a known malware source on your host.<br>(Applies to: App Service on Linux) | Privilege Escalation, Execution, Exfiltration, Command and Control | Medium |

articles/expressroute/expressroute-monitoring-metrics-alerts.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -112,6 +112,10 @@ You can view near to real-time availability of BGP (Layer-3 connectivity) across
112112

113113
:::image type="content" source="./media/expressroute-monitoring-metrics-alerts/erBgpAvailabilityMetrics.jpg" alt-text="BGP availability per peer":::
114114

115+
>[!NOTE]
116+
>During maintenance between the Microsoft edge and core network, BGP availability will appear down even if the BGP session between the customer edge and Microsoft edge remains up. For information about maintenance between the Microsoft edge and core network, make sure to have your [maintenance alerts turned on and configured](./maintenance-alerts.md).
117+
>
118+
115119
### <a name = "arp"></a>ARP Availability - Split by Peering
116120

117121
Aggregation type: *Avg*

articles/expressroute/expressroute-network-insights.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,10 @@ The *Availability* tab tracks ARP and BGP availability, plotting the data for bo
5252

5353
:::image type="content" source="./media/expressroute-network-insights/arp-bgp-availability.png" alt-text="Screenshot of availability metric graphs." lightbox="./media/expressroute-network-insights/arp-bgp-availability-expanded.png":::
5454

55+
>[!NOTE]
56+
>During maintenance between the Microsoft edge and core network, BGP availability will appear down even if the BGP session between the customer edge and Microsoft edge remains up. For information about maintenance between the Microsoft edge and core network, make sure to have your [maintenance alerts turned on and configured](./maintenance-alerts.md).
57+
>
58+
5559
### Throughput
5660

5761
Similarly, the *Throughput* tab plots the total throughput of ingress and egress traffic for the circuit in bits/second. You can also view throughput for individual connections and each type of configured peering.

articles/expressroute/maintenance-alerts.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ ExpressRoute uses Azure Service Health to notify you of planned and upcoming Exp
1616
> [!NOTE]
1717
> * During a maintenance activity or in case of unplanned events impacting one of the connection, Microsoft will prefer to use AS path prepending to drain traffic over to the healthy connection. You will need to ensure the traffic is able to route over the healthy path when path prepend is configured from Microsoft and required route advertisements are configured appropriately to avoid any service disruption.
1818
> * Terminating ExpressRoute BGP connections on stateful devices can cause issues with failover during planned or unplanned maintenances by Microsoft or your ExpressRoute Provider. You should test your set up to ensure your traffic will failover properly, and when possible, terminate BGP sessions on stateless devices.
19+
> * During maintenance between the Microsoft edge and core network, BGP availability will appear down even if the BGP session between the customer edge and Microsoft edge remains up. For information about maintenance between the Microsoft edge and core network, make sure to have your maintenance alerts turned on and configured correctly using the guidance below.
1920
>
2021
2122
## View planned maintenance

articles/expressroute/monitor-expressroute.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -141,6 +141,10 @@ The following table lists common and recommended alert rules for ExpressRoute.
141141
| ARP availability down | Dimension name: Peering Type, Aggregation type: Avg, Operator: Less than, Threshold value: 100% | When ARP availability is down for a peering type. |
142142
| BGP availability down | Dimension name: Peer, Aggregation type: Avg, Operator: Less than, Threshold value: 100% | When BGP availability is down for a peer. |
143143
144+
>[!NOTE]
145+
>During maintenance between the Microsoft edge and core network, BGP availability will appear down even if the BGP session between the customer edge and Microsoft edge remains up. For information about maintenance between the Microsoft edge and core network, make sure to have your [maintenance alerts turned on and configured](./maintenance-alerts.md).
146+
>
147+
144148
### Alerts for ExpressRoute gateway connections
145149
146150
1. To configure alerts, navigate to **Azure Monitor**, then select **Alerts**.

articles/hdinsight/hdinsight-for-vscode.md

Lines changed: 7 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ With Spark & Hive Tools for Visual Studio Code, you can submit interactive Hive
164164

165165
- **MESSAGES** panel: When you select a **Line** number, it jumps to the first line of the running script.
166166

167-
## Submit interactive PySpark queries
167+
## Submit interactive PySpark queries (Not supported Synapse PySpark interactive anymore)
168168

169169
Users can perform PySpark interactive in the following ways:
170170

@@ -260,7 +260,8 @@ The tool also supports the **Spark SQL** query:
260260

261261
> [!NOTE]
262262
>
263-
> [ms-toolsai.jupyter >2021.3.684299474 version is not supported on this extension](#known-issues) is a known issue. Please using Synapse kernel by sticking to Microsoft Jupyter 2021.3.684299474.
263+
> [For Synapse PySpark installation error](#known-issues), since its dependency will not be maintained anymore by other team, this will not be maintained anymore as well. If you trying to use Synapse Pyspark interactive, please switch to use [Azure Synapse Analytics](https://ms.web.azuresynapse.net/en-us/) instead. And it's a long term change.
264+
>
264265
265266
## Submit PySpark batch job
266267

@@ -311,7 +312,7 @@ You can follow the normal steps to sign in to Azure subscription to connect to y
311312

312313
For run a hive job, you can follow the normal steps to submit job to HDInsight ESP cluster with ID Broker (HIB). Refer to [Submit interactive Hive queries and Hive batch scripts](#submit-interactive-hive-queries-and-hive-batch-scripts) for more instructions.
313314

314-
For run a interactive PySpark job, you can follow the normal steps to submit job to HDInsight ESP cluster with ID Broker (HIB). Refer to [Submit interactive PySpark queries](#submit-interactive-pyspark-queries) for more instructions.
315+
For run an interactive PySpark job, you can follow the normal steps to submit job to HDInsight ESP cluster with ID Broker (HIB). Refer to Submit interactive PySpark queries.
315316

316317
For run a PySpark batch job, you can follow the normal steps to submit job to HDInsight ESP cluster with ID Broker (HIB). Refer to [Submit PySpark batch job](#submit-pyspark-batch-job) for more instructions.
317318

@@ -483,17 +484,11 @@ From the menu bar, go to **View** > **Command Palette**, and then enter **Azure:
483484

484485
## Known Issues
485486

486-
ms-toolsai.jupyter >2021.3.684299474 version is not supported on this extension, please using Synapse kernel by sticking to Microsoft Jupyter 2021.3.684299474.
487-
488-
1. Disable auto updating extension.
489-
490-
![disable auto updating extension](./media/hdinsight-for-vscode/disable-auto-updating-extension.png)
491-
492-
2. Install a selected version of Microsoft Jupyter.
487+
### Synapse PySpark installation error.
493488

494-
![selected version of microsoft jupyter](./media/hdinsight-for-vscode/selected-version-of-microsoft-jupyter.png)
489+
For Synapse PySpark installation error, since its dependency will not be maintained anymore by other team, it will not be maintained anymore. If you trying to use Synapse Pyspark interactive, please use [Azure Synapse Analytics](https://ms.web.azuresynapse.net/) instead. And it's a long term change.
495490

496-
3. Install Microsoft Jupyter version 2021.3.684299474
491+
![synapse pyspark installation error](./media/hdinsight-for-vscode/known-issue.png)
497492

498493

499494
## Next steps
-1.47 KB
Loading

0 commit comments

Comments
 (0)