Skip to content

Commit 71db233

Browse files
authored
Merge pull request #111080 from MicrosoftDocs/master
Merge master to live Sunday 4:00 PM
2 parents 2f012ae + be191ad commit 71db233

19 files changed

+216
-294
lines changed

.openpublishing.redirection.json

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -423,12 +423,17 @@
423423
},
424424
{
425425
"source_path": "articles/active-directory/saas-apps/realtimeboard-tutorial.md",
426-
"redirect_url": "/articles/active-directory/saas-apps/miro-tutorial",
426+
"redirect_url": "/azure/active-directory/saas-apps/miro-tutorial",
427427
"redirect_document_id": false
428428
},
429429
{
430430
"source_path": "articles/active-directory/saas-apps/redbrickhealth-tutorial.md",
431-
"redirect_url": "/articles/active-directory/saas-apps/redbrick-health-tutorial",
431+
"redirect_url": "/azure/active-directory/saas-apps/redbrick-health-tutorial",
432+
"redirect_document_id": false
433+
},
434+
{
435+
"source_path": "articles/active-directory/saas-apps/adobe-identity-management-tutorial.md",
436+
"redirect_url": "/azure/active-directory/saas-apps/tutorial-list",
432437
"redirect_document_id": false
433438
},
434439
{
@@ -40082,12 +40087,12 @@
4008240087
},
4008340088
{
4008440089
"source_path": "articles/iot-central/tutorial-add-device-pnp.md",
40085-
"redirect_url": "/azure/iot-central/core/tutorial-connect-pnp-device",
40090+
"redirect_url": "/azure/iot-central/core/quick-create-pnp-device",
4008640091
"redirect_document_id": false
4008740092
},
4008840093
{
4008940094
"source_path": "articles/iot-central/tutorial-define-device-type-pnp.md",
40090-
"redirect_url": "/azure/iot-central/core/howto-set-up-template",
40095+
"redirect_url": "/azure/iot-central/core/quick-create-pnp-device",
4009140096
"redirect_document_id": false
4009240097
},
4009340098
{
@@ -46282,7 +46287,7 @@
4628246287
},
4628346288
{
4628446289
"source_path": "articles/iot-central/quick-create-pnp-device-pnp.md",
46285-
"redirect_url": "/azure/iot-central/core/quick-create-simulated-device/",
46290+
"redirect_url": "/azure/iot-central/core/quick-create-pnp-device/",
4628646291
"redirect_document_id": false
4628746292
},
4628846293
{
@@ -46347,12 +46352,7 @@
4634746352
},
4634846353
{
4634946354
"source_path": "articles/iot-central/core/quick-create-pnp-device-pnp.md",
46350-
"redirect_url": "/azure/iot-central/core/quick-create-simulated-device/",
46351-
"redirect_document_id": false
46352-
},
46353-
{
46354-
"source_path": "articles/iot-central/core/quick-create-pnp-device.md",
46355-
"redirect_url": "/azure/iot-central/core/quick-create-simulated-device/",
46355+
"redirect_url": "/azure/iot-central/core/quick-create-pnp-device/",
4635646356
"redirect_document_id": false
4635746357
},
4635846358
{
@@ -46787,7 +46787,7 @@
4678746787
},
4678846788
{
4678946789
"source_path": "articles/iot-central/preview/quick-create-pnp-device.md",
46790-
"redirect_url": "/azure/iot-central/core/quick-create-simulated-device/",
46790+
"redirect_url": "/azure/iot-central/core/quick-create-pnp-device/",
4679146791
"redirect_document_id": false
4679246792
},
4679346793
{

articles/active-directory/saas-apps/adobe-identity-management-tutorial.md

Lines changed: 0 additions & 152 deletions
This file was deleted.

articles/active-directory/saas-apps/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,8 +47,6 @@
4747
href: adobe-creative-cloud-tutorial.md
4848
- name: Adobe Experience Manager
4949
href: adobeexperiencemanager-tutorial.md
50-
- name: Adobe Identity Management
51-
href: adobe-identity-management-tutorial.md
5250
- name: Adobe Sign
5351
href: adobe-echosign-tutorial.md
5452
- name: Adoddle cSaas Platform

articles/azure-monitor/platform/alerts-dynamic-thresholds.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,8 @@ When an alert rule is first created, the thresholds appearing in the chart are c
8888

8989
## How much data is needed to trigger an alert?
9090

91-
If you have a new resource or missing metric data, Dynamic Thresholds won't trigger alerts before three days or 30 samples of metric data are available to ensure accurate thresholds.
91+
If you have a new resource or missing metric data, Dynamic Thresholds won't trigger alerts before three days and at least 30 samples of metric data are available, to ensure accurate thresholds.
92+
For existing resources with sufficient metric data, Dynamic Thresholds can trigger alerts immediately.
9293

9394
## Dynamic Thresholds best practices
9495

articles/azure-monitor/platform/customer-managed-keys.md

Lines changed: 44 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.subservice: logs
55
ms.topic: conceptual
66
author: yossi-y
77
ms.author: yossiy
8-
ms.date: 04/08/2020
8+
ms.date: 04/12/2020
99

1010
---
1111
# Azure Monitor customer-managed key configuration
@@ -148,20 +148,43 @@ GET https://management.azure.com/subscriptions/ subscription-id/providers/Micros
148148
Authorization: Bearer <token>
149149
```
150150

151-
The body of the response from the operation contains information about the operation including *Status*. The asynchronous operations in this configuration and their statuses are:
151+
The response contains information about the operation and its *Status*. It can be one of the followings:
152152

153-
* Creating a *Cluster* resource
154-
* ProvisioningAccount -- ADX cluster is in provisioning
155-
* Succeeded -- provisioning is completed
156-
157-
* Granting permissions to your Key Vault
158-
* Updating -- Key identifier details update is in progress
159-
* Succeeded -- update completed
153+
Operation is in progress
154+
```json
155+
{
156+
"id": "Azure-AsyncOperation URL value from the GET operation",
157+
"name": "operation-id",
158+
"status" : "InProgress",
159+
"startTime": "2017-01-06T20:56:36.002812+00:00",
160+
}
161+
```
160162

161-
* Associating Log Analytics workspaces
162-
* Linking -- workspace association to cluster is in progress
163-
* Succeeded -- association completed
163+
Operation is completed
164+
```json
165+
{
166+
"id": "Azure-AsyncOperation URL value from the GET operation",
167+
"name": "operation-id",
168+
"status" : "Succeeded",
169+
"startTime": "2017-01-06T20:56:36.002812+00:00",
170+
"endTime": "2017-01-06T20:56:56.002812+00:00",
171+
}
172+
```
164173

174+
Operation failed
175+
```json
176+
{
177+
"id": "Azure-AsyncOperation URL value from the GET operation",
178+
"name": "operation-id",
179+
"status" : "Failed",
180+
"startTime": "2017-01-06T20:56:36.002812+00:00",
181+
"endTime": "2017-01-06T20:56:56.002812+00:00",
182+
"error" : {
183+
"code": "error-code",
184+
"message": "error-message"
185+
}
186+
}
187+
```
165188

166189
### Subscription whitelisting
167190

@@ -215,7 +238,8 @@ The identity is assigned to the *Cluster* resource at creation time.
215238

216239
**Response**
217240

218-
200 OK and header when accepted.
241+
200 OK and header.
242+
219243
>[!Important]
220244
> During the early access period of the feature, the ADX cluster is provisioned manually. While it takes the provisioning of the underly ADX cluster a while to complete, you can check the provisioning state in two ways:
221245
> 1. Copy the Azure-AsyncOperation URL value from the response and follow the [asynchronous operations status check](#asynchronous-operations-and-status-check).
@@ -317,7 +341,8 @@ Content-type: application/json
317341

318342
**Response**
319343

320-
200 OK and header when accepted.
344+
200 OK and header.
345+
321346
>[!Important]
322347
> It takes the propagation of the Key identifier a few minutes to complete. You can check the provisioning state in two ways:
323348
> 1. Copy the Azure-AsyncOperation URL value from the response and follow the [asynchronous operations status check](#asynchronous-operations-and-status-check).
@@ -385,11 +410,12 @@ Content-type: application/json
385410

386411
**Response**
387412

388-
200 OK and header when accepted.
389-
>[!Important]
390-
> Ingested data is stored encrypted with your managed key after association operation, which can take up to 90 minutes to complete. To check the workspace association state, copy the Azure-AsyncOperation URL value from the response and follow the [asynchronous operations status check](#asynchronous-operations-and-status-check).
413+
200 OK and header.
391414

392-
You can verify if your workspace was associated to a Cluster resource by sending a GET request to [Workspaces – Get](https://docs.microsoft.com/rest/api/loganalytics/workspaces/get) and observing the response. The clusterResourceId indicates on the Cluster resource ID.
415+
>[!Important]
416+
> Ingested data is stored encrypted with your managed key after association operation, which can take up to 90 minutes to complete. You can check the workspace association state in two ways:
417+
> 1. Copy the Azure-AsyncOperation URL value from the response and follow the [asynchronous operations status check](#asynchronous-operations-and-status-check).
418+
> 2. Send a [Workspaces – Get](https://docs.microsoft.com/rest/api/loganalytics/workspaces/get) request and observe the response, associated workspace will have a clusterResourceId under "features".
393419
394420
```rest
395421
GET https://management.azure.com/subscriptions/<subscription-id>/resourcegroups/<resource-group-name>/providers/microsoft.operationalInsights/workspaces/<workspace-name>?api-version=2015-11-01-preview

articles/backup/backup-azure-arm-restore-vms.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,6 @@ Azure Backup provides a number of ways to restore a VM.
2222

2323
> [!NOTE]
2424
> You can also recover specific files and folders on an Azure VM. [Learn more](backup-azure-restore-files-from-vm.md).
25-
>
26-
> If you're running the [latest version](backup-instant-restore-capability.md) of Azure Backup for Azure VMs (known as Instant Restore), snapshots are kept for up to seven days, and you can restore a VM from snapshots before the backup data is sent to the vault. If you want to restore a VM from a backup from the last seven days, it's quicker to restore from the snapshot and not from the vault.
2725
2826
## Storage accounts
2927

articles/backup/backup-azure-file-folder-backup-faq.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ The latest MARS agent used when backing up Windows Server machines, System Cente
1818

1919
### How long are vault credentials valid?
2020

21-
Vault credentials expire after 48 hours. If the credentials file expires, download the file again from the Azure portal.
21+
Vault credentials expire after 10 days. If the credentials file expires, download the file again from the Azure portal.
2222

2323
### From what drives can I back up files and folders?
2424

@@ -182,7 +182,6 @@ If you have the same passphrase (that you provided during registration) of the o
182182
| Lost |Available |You can install and register the MARS agent on another machine with the same passphrase that you provided during registration of the original machine. Choose **Recovery Option** > **Another location** to perform your restore. For more information, see this [article](https://docs.microsoft.com/azure/backup/backup-azure-restore-windows-server#use-instant-restore-to-restore-data-to-an-alternate-machine).
183183
| Lost |Lost |Not possible to recover the data or data is not available |
184184
185-
186185
### What happens if I cancel an ongoing restore job?
187186
188187
If an ongoing restore job is canceled, the restore process stops. All files restored before the cancellation stay in configured destination (original or alternate location), without any rollbacks.

articles/lab-services/classroom-labs/how-to-manage-classroom-labs.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.workload: na
1212
ms.tgt_pltfrm: na
1313
ms.devlang: na
1414
ms.topic: how-to
15-
ms.date: 02/20/2020
15+
ms.date: 04/10/2020
1616
ms.author: spelluru
1717

1818
---
@@ -33,6 +33,8 @@ To set up a classroom lab in a lab account, you must be a member of the **Lab Cr
3333
1. Specify a **name** for your lab.
3434
2. Select the **size of the virtual machines** you need for the class. For the list of sizes available, see the [VM Sizes](#vm-sizes) section.
3535
3. Select the **virtual machine image** that you want to use for the classroom lab. If you select a Linux image, you see an option to enable remote desktop connection for it. For details, see [Enable remote desktop connection for Linux](how-to-enable-remote-desktop-linux.md).
36+
37+
If you signed in using lab account owner credentials, you will see an option to enable more images for the lab. For more information, see [Enable images at the time of lab creation](specify-marketplace-images.md#enable-images-at-the-time-of-lab-creation).
3638
4. Review the **total price per hour** displayed on the page.
3739
6. Select **Save**.
3840

0 commit comments

Comments
 (0)