Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 4b288a5

Browse files
committedJun 16, 2020
renamed images
1 parent 93122ac commit 4b288a5

11 files changed

+7
-7
lines changed
 

‎articles/devtest-labs/devtest-lab-configure-cost-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ DevTest Labs lets you better manage the costs in your lab by setting a spending
7171
- **Plot on chart**: When this threshold is met, the results are plotted on the cost trend graph that you can view, as described in Viewing the Monthly Estimated Cost Trend chart.
7272
- If you choose to **Notify** when the threshold is met, you must specify a webhook URL. In the Cost integrations area, select **Click here to add an integration**. Enter a **Webhook URL** in the Configure notification pane and then select **OK**.
7373

74-
![Configure notification pane](./media/devtest-lab-configure-cost-management/configure-notification.png)
74+
![Configure notification pane](./media/devtest-lab-configure-cost-management/configure-notification-new.png)
7575

7676
- If you specify **Notify**, you must define a webhook URL.
7777
- Likewise, if you define a webhook URL, you must set **Notification** to **On** in the Cost threshold pane.

‎articles/devtest-labs/devtest-lab-scale-lab.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -36,11 +36,11 @@ These steps show you how to view the current quotas in your subscription for spe
3636
1. In the Billing blade, select a subscription.
3737
4. Select **Usage + quotas**.
3838

39-
![Usage and quotas button](./media/devtest-lab-scale-lab/devtestlab-usage-and-quotas.png)
39+
![Usage and quotas button](./media/devtest-lab-scale-lab/devtestlab-usage-and-quotas-new.png)
4040

4141
The Usage + quotas blade appears, listing different resources available in that subscription and the percentage of the quota that is being used per resource.
4242

43-
![Quotas and usage](./media/devtest-lab-scale-lab/devtestlab-view-quotas.png)
43+
![Quotas and usage](./media/devtest-lab-scale-lab/devtestlab-view-quotas-new.png)
4444

4545
## Requesting more resources in your subscription
4646
If you reach a quota cap, the default limit of a resource in a subscription can be increased up to a maximum limit, as described in [Azure Subscription and Service Limits](https://docs.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits).
@@ -50,11 +50,11 @@ These steps show you how to request a quota increase through the [Azure portal](
5050
1. Select **More Services**, select **Billing**, and then select **Usage + quotas**.
5151
1. In the Usage + quotas blade, select the **Request Increase** button.
5252

53-
![Request increase button](./media/devtest-lab-scale-lab/devtestlab-request-increase.png)
53+
![Request increase button](./media/devtest-lab-scale-lab/devtestlab-request-increase-new.png)
5454

5555
1. To complete and submit the request, fill out the required information on all three tabs of the **New support request** form.
5656

57-
![Request increase form](./media/devtest-lab-scale-lab/devtestlab-support-form.png)
57+
![Request increase form](./media/devtest-lab-scale-lab/devtestlab-support-form-new.png)
5858

5959
[Understanding Azure Limits and Increases](https://azure.microsoft.com/blog/azure-limits-quotas-increase-requests/) provides more information about contacting Azure support to request a quota increase.
6060

‎articles/devtest-labs/devtest-lab-troubleshoot-artifact-failure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ After you have created an artifact, you can check to see whether it succeeded or
3232
2. Choose the Windows VM that includes the artifact that you want to investigate.
3333
3. In the left panel, under **GENERAL**, select **Artifacts**. A list of artifacts associated with that VM appears. The name of the artifact and the artifact status are indicated.
3434

35-
![Artifact status](./media/devtest-lab-troubleshoot-artifact-failure/devtest-lab-artifacts-failure.png)
35+
![Artifact status](./media/devtest-lab-troubleshoot-artifact-failure/devtest-lab-artifacts-failure-new.png)
3636

3737
4. Select an artifact that shows a **Failed** status. The artifact opens. An extension message that includes details about the failure of the artifact is displayed.
3838

@@ -44,7 +44,7 @@ After you have created an artifact, you can check to see whether it succeeded or
4444
1. Sign in to the VM that contains the artifact you want to diagnose.
4545
2. Go to C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension\\*1.9*\Status, where *1.9* is the Azure Custom Script Extension version number.
4646

47-
![The Status file](./media/devtest-lab-troubleshoot-artifact-failure/devtest-lab-artifact-error-vm-status.png)
47+
![The Status file](./media/devtest-lab-troubleshoot-artifact-failure/devtest-lab-artifact-error-vm-status-new.png)
4848

4949
3. Open the **status** file.
5050

0 commit comments

Comments
 (0)
Please sign in to comment.