Skip to content

Commit 510e06a

Browse files
authored
Merge pull request #113117 from ianmsgit/ali-fixes-2
ALI fixes
2 parents cd470e5 + 88ef419 commit 510e06a

File tree

2 files changed

+6
-10
lines changed

2 files changed

+6
-10
lines changed

articles/azure-large-instances/find-your-subscription-id.md

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,10 @@ ms.date: 06/01/2023
1414
This article explains how to find your Azure Large Instances subscription ID.
1515

1616
A *Subscription ID* is a unique identifier for your service in Azure.
17-
You need it when interacting with the Microsoft Support team. To find your subscription ID, follow these steps:
17+
You need it when interacting with the Microsoft Support team.
18+
To find your subscription ID, follow these steps:
1819

1920
1. Go to [Azure support portal](https://portal.Azure.Com)
20-
2. From the left pane, select **Subscriptions**.
21-
3. A new blade called “Subscriptions” will open to display your subscriptions.
22-
23-
1. Choose the subscription you have used for Azure Large Instances.
24-
25-
26-
27-
21+
2. In **Azure services**, select **Subscriptions**.
22+
The **Subscriptions** blade appears, displaying your subscriptions.
23+
3. Choose the subscription you have used for Azure Large Instances.

articles/azure-large-instances/quality-checks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.date: 06/01/2023
1313
# Quality checks for Azure Large Instances
1414
This article provides an overview of Azure Large Instances for Epic<sup>®</sup> quality checks.
1515

16-
The Microsoft operations team performs a series of extensive quality checks to ensure that customers' requests to run Azure Large Instances for Epic<sup>®</sup> are fulfilled accurately, and that infrastructure is healthy before handover.
16+
The Microsoft operations team performs a series of extensive quality checks to ensure that customers' requests to run Azure Large Instances for Epic are fulfilled accurately, and that infrastructure is healthy before handover.
1717
However, customers are advised to perform their own checks to ensure services have been provided as requested, including the following:
1818

1919
* Basic connectivity

0 commit comments

Comments
 (0)