Skip to content

Commit f3007b9

Browse files
committed
Fixing portal links 4
1 parent 76a2734 commit f3007b9

File tree

100 files changed

+148
-148
lines changed

Some content is hidden

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

100 files changed

+148
-148
lines changed

articles/defender-for-iot/device-builders/how-to-manage-device-inventory-on-the-cloud.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ The following table describes the different device properties in the device inve
4949

5050
**To view the device inventory**:
5151

52-
1. Open the [Azure portal](https://ms.portal.azure.com).
52+
1. Open the [Azure portal](https://portal.azure.com).
5353

5454
1. Navigate to **Defender for IoT** > **Device inventory**.
5555

@@ -119,7 +119,7 @@ If you are under the impression that certain devices are not actively communicat
119119

120120
**To identify all devices that have not communicated recently**:
121121

122-
1. Open the [Azure portal](https://ms.portal.azure.com).
122+
1. Open the [Azure portal](https://portal.azure.com).
123123

124124
1. Navigate to **Defender for IoT** > **Device inventory**.
125125

articles/defender-for-iot/device-builders/quickstart-onboard-iot-hub.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ You can onboard Defender for IoT to an existing IoT Hub, where you can then moni
3939

4040
**To enable Defender for IoT on an existing IoT Hub**:
4141

42-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
42+
1. Sign in to the [Azure portal](https://portal.azure.com/).
4343

4444
1. Navigate to **IoT Hub** > **`Your hub`** > **Defender for IoT** > **Overview**.
4545

@@ -55,7 +55,7 @@ The **Secure your IoT solution** button will only appear if the IoT Hub has not
5555

5656
**To verify that Defender for IoT is enabled**:
5757

58-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
58+
1. Sign in to the [Azure portal](https://portal.azure.com/).
5959

6060
1. Navigate to **IoT Hub** > **`Your hub`** > **Defender for IoT** > **Overview**.
6161

articles/defender-for-iot/device-builders/tutorial-configure-agent-based-solution.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ In this tutorial you will learn how to:
3434

3535
**To enable data collection**:
3636

37-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
37+
1. Sign in to the [Azure portal](https://portal.azure.com/).
3838

3939
1. Navigate to **IoT Hub** > **`Your hub`** > **Defender for IoT** > **Settings** > **Data Collection**.
4040

@@ -63,7 +63,7 @@ You can choose to add storage of an additional information type as `raw events`.
6363
6464
**To enable Log Analytics to work with micro agent**:
6565

66-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
66+
1. Sign in to the [Azure portal](https://portal.azure.com/).
6767

6868
1. Navigate to **IoT Hub** > **`Your hub`** > **Defender for IoT** > **Settings** > **Data Collection**.
6969

@@ -87,7 +87,7 @@ In order to secure your IoT solution, the IP addresses of the incoming, and outg
8787

8888
**To enable the collection of IP address data**:
8989

90-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
90+
1. Sign in to the [Azure portal](https://portal.azure.com/).
9191

9292
1. Navigate to **IoT Hub** > **`Your hub`** > **Defender for IoT** > **Settings** > **Data Collection**.
9393

articles/defender-for-iot/device-builders/tutorial-configure-your-solution.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ In this tutorial you'll learn how to:
3535

3636
**To add new resource to your IoT solution**:
3737

38-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
38+
1. Sign in to the [Azure portal](https://portal.azure.com/).
3939

4040
1. Search for, and select **IoT Hub**.
4141

articles/defender-for-iot/device-builders/tutorial-create-micro-agent-module-twin.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ A `DefenderIotMicroAgent` module twin can be created by manually editing each mo
5858

5959
**To create a DefenderIotMicroAgent module twin for a device**:
6060

61-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
61+
1. Sign in to the [Azure portal](https://portal.azure.com/).
6262

6363
1. Navigate to **IoT Hub** > **`Your hub`** > **Device management** > **Devices**.
6464

@@ -74,7 +74,7 @@ A `DefenderIotMicroAgent` module twin can be created by manually editing each mo
7474

7575
**To verify the creation of a DefenderIotMicroAgent module twin on a specific device**:
7676

77-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
77+
1. Sign in to the [Azure portal](https://portal.azure.com/).
7878

7979
1. Navigate to **IoT Hub** > **`Your hub`** > **Device management** > **Devices**.
8080

articles/defender-for-iot/device-builders/tutorial-investigate-security-alerts.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The Defender for IoT security alert list displays all of the aggregated security
4040

4141
**To investigate security alerts**:
4242

43-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
43+
1. Sign in to the [Azure portal](https://portal.azure.com/).
4444

4545
1. Navigate to **IoT Hub** > **`Your hub`** > **Defender for IoT** > **Security Alerts**.
4646

@@ -52,7 +52,7 @@ Opening each aggregated alert displays the detailed alert description, remediati
5252

5353
**To investigate security alert details**:
5454

55-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
55+
1. Sign in to the [Azure portal](https://portal.azure.com/).
5656

5757
1. Navigate to **IoT Hub** > **`Your hub`** > **Defender for IoT** > **Security Alerts**.
5858

@@ -72,7 +72,7 @@ You can access your alerts and investigate them with the Log Analytics workspace
7272

7373
**To access your alerts in your Log Analytics workspace after configuration**:
7474

75-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
75+
1. Sign in to the [Azure portal](https://portal.azure.com/).
7676

7777
1. Navigate to **IoT Hub** > **`Your hub`** > **Defender for IoT** > **Security Alerts**.
7878

articles/defender-for-iot/device-builders/tutorial-investigate-security-recommendations.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ In this tutorial you will learn how to:
3838

3939
The IoT Hub recommendations list displays all of the aggregated security recommendations for your IoT Hub.
4040

41-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
41+
1. Sign in to the [Azure portal](https://portal.azure.com/).
4242

4343
1. Navigate to **IoT Hub** > **`Your hub`** > **Defender for IoT** > **Recommendations**.
4444

@@ -48,7 +48,7 @@ The IoT Hub recommendations list displays all of the aggregated security recomme
4848

4949
Open each aggregated recommendation to display the detailed recommendation description, remediation steps, device ID for each device that triggered a recommendation. It also displays recommendation severity and direct-investigation access using Log Analytics.
5050

51-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
51+
1. Sign in to the [Azure portal](https://portal.azure.com/).
5252

5353
1. Navigate to **IoT Hub** > **`Your hub`** > **Defender for IoT** > **Recommendations**.
5454

@@ -66,7 +66,7 @@ Open each aggregated recommendation to display the detailed recommendation descr
6666

6767
**To access your recommendations in Log Analytics workspace**:
6868

69-
1. Sign in to the [Azure portal](https://ms.portal.azure.com/).
69+
1. Sign in to the [Azure portal](https://portal.azure.com/).
7070

7171
1. Navigate to **IoT Hub** > **`Your hub`** > **Defender for IoT** > **Recommendations**.
7272

articles/defender-for-iot/organizations/how-to-manage-device-inventory-for-organizations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ The following table describes the different device properties in the device inve
6666

6767
**To view the device inventory**:
6868

69-
1. Open the [Azure portal](https://ms.portal.azure.com).
69+
1. Open the [Azure portal](https://portal.azure.com).
7070

7171
1. Navigate to **Defender for IoT** > **Device inventory**.
7272

@@ -136,7 +136,7 @@ If you are under the impression that certain devices are not actively communicat
136136

137137
**To identify all devices that have not communicated recently**:
138138

139-
1. Open the [Azure portal](https://ms.portal.azure.com).
139+
1. Open the [Azure portal](https://portal.azure.com).
140140

141141
1. Navigate to **Defender for IoT** > **Device inventory**.
142142

articles/digital-twins/how-to-manage-routes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -156,7 +156,7 @@ az resource create --id <Azure-Digital-Twins-instance-Azure-resource-ID>/endpoin
156156

157157
When an endpoint can't deliver an event within a certain time period or after trying to deliver the event a certain number of times, it can send the undelivered event to a storage account. This process is known as **dead-lettering**.
158158

159-
You can set up the necessary storage resources using the [Azure portal](https://ms.portal.azure.com/#home) or the [Azure Digital Twins CLI](/cli/azure/dt). However, to create an endpoint with dead-lettering enabled, you'll need use the [Azure Digital Twins CLI](/cli/azure/dt) or [control plane APIs](concepts-apis-sdks.md#overview-control-plane-apis).
159+
You can set up the necessary storage resources using the [Azure portal](https://portal.azure.com/#home) or the [Azure Digital Twins CLI](/cli/azure/dt). However, to create an endpoint with dead-lettering enabled, you'll need use the [Azure Digital Twins CLI](/cli/azure/dt) or [control plane APIs](concepts-apis-sdks.md#overview-control-plane-apis).
160160

161161
To learn more about dead-lettering, see [Endpoints and event routes](concepts-route-events.md#dead-letter-events). For instructions on how to set up an endpoint with dead-lettering, continue through the rest of this section.
162162

@@ -177,7 +177,7 @@ Next, create a **SAS token** for your storage account that the endpoint can use
177177

178178
# [Portal](#tab/portal)
179179

180-
1. Start by navigating to your storage account in the [Azure portal](https://ms.portal.azure.com/#home) (you can find it by name with the portal search bar).
180+
1. Start by navigating to your storage account in the [Azure portal](https://portal.azure.com/#home) (you can find it by name with the portal search bar).
181181
1. In the storage account page, choose the _Shared access signature_ link in the left navigation bar to start setting up the SAS token.
182182

183183
:::image type="content" source="./media/how-to-manage-routes/generate-sas-token-1.png" alt-text="Screenshot of the storage account page in the Azure portal." lightbox="./media/how-to-manage-routes/generate-sas-token-1.png":::

articles/digital-twins/reference-service-limits.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The following sections describe the service limits of Azure Digital Twins.
2222
> [!NOTE]
2323
> Some areas of this service have adjustable limits. This is represented in the tables below with the *Adjustable?* column. When the limit can be adjusted, the *Adjustable?* value is *Yes*.
2424
>
25-
> If your business requires raising an adjustable limit or quota above the default limit, you can request additional resources by [opening a support ticket](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
25+
> If your business requires raising an adjustable limit or quota above the default limit, you can request additional resources by [opening a support ticket](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
2626
2727
## Limits by type
2828

0 commit comments

Comments
 (0)