Skip to content

Commit 694b14b

Browse files
committed
Acrolinx updates
1 parent ac06b54 commit 694b14b

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

articles/synapse-analytics/troubleshoot/troubleshoot-synapse-studio-powershell.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -7,14 +7,15 @@ ms.subservice: troubleshooting
77
ms.topic: conceptual
88
ms.date: 10/30/2020
99
ms.author: whhender
10-
ms.reviewer: sngun
10+
ms.reviewer: whhender
1111
---
1212

1313
# Troubleshoot Synapse Studio connectivity with PowerShell
1414

15-
Azure Synapse Studio depends on a set of Web API endpoints to work properly. This guide will help you identify causes of connectivity issues when you're:
16-
- configuring your local network (such as network behind a corporate firewall) for accessing Azure Synapse Studio.
17-
- experiencing connectivity issues using Azure Synapse Studio.
15+
Azure Synapse Studio depends on a set of Web API endpoints to work properly. This guide will help you identify causes of connectivity issues when:
16+
17+
- You're configuring your local network (such as network behind a corporate firewall) for accessing Azure Synapse Studio.
18+
- You're experiencing connectivity issues using Azure Synapse Studio.
1819

1920
## Prerequisite
2021

@@ -27,7 +28,7 @@ Right-click on the following link, and select "Save target as":
2728

2829
- [Test-AzureSynapse.ps1](https://go.microsoft.com/fwlink/?linkid=2119734)
2930

30-
Alternatively, you may open the link directly, and save the opened script file. Don't save the address of the link above, as it may change in the future.
31+
Alternatively, you can open the link directly, and save the opened script file. Don't save the address of the link, as it could change in the future.
3132

3233
In file explorer, right-click on the downloaded script file, and select "Run with PowerShell".
3334

@@ -41,16 +42,16 @@ The diagnostic session will be started. Wait for it to complete.
4142

4243
![Wait for diagnosis to complete](media/troubleshooting-synapse-studio-powershell/wait-for-diagnosis.png)
4344

44-
In the end, a diagnosis summary will be shown. If your PC cannot connect to one or more of the endpoints, it will show some suggestions in the "Summary" section.
45+
In the end, a diagnosis summary will be shown. If your PC can't connect to one or more of the endpoints, it will show some suggestions in the "Summary" section.
4546

4647
![Review diagnostic summary](media/troubleshooting-synapse-studio-powershell/diagnosis-summary.png)
4748

48-
Additionally, a diagnostic log file for this session will be generated in the same folder as the troubleshooting script. Its location is shown in "General tips" section (`D:\TestAzureSynapse_2020....log`). You may send this file to technical support if necessary.
49+
Additionally, a diagnostic log file for this session will be generated in the same folder as the troubleshooting script. Its location is shown in "General tips" section (`D:\TestAzureSynapse_2020....log`). You can send this file to technical support if necessary.
4950

50-
If you're a network administrator and tuning your firewall configuration for Azure Synapse Studio, the technical details shown above the "Summary" section may help.
51+
If you're a network administrator and tuning your firewall configuration for Azure Synapse Studio, the technical details shown above the "Summary" section might help.
5152

5253
* All the test items (requests) marked with "Passed" mean they have passed connectivity tests, regardless of the HTTP status code.
53-
For the failed requests, the reason is shown in yellow, such as `NamedResolutionFailure` or `ConnectFailure`. These reasons may help you figure out whether there are misconfigurations with your network environment.
54+
For the failed requests, the reason is shown in yellow, such as `NamedResolutionFailure` or `ConnectFailure`. These reasons might help you figure out whether there are misconfigurations with your network environment.
5455

5556

5657
## Next steps

0 commit comments

Comments
 (0)