Skip to content

Commit 59d51bc

Browse files
Learn Build Service GitHub AppLearn Build Service GitHub App
authored andcommitted
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents 102ba02 + 363d4bd commit 59d51bc

File tree

48 files changed

+575
-323
lines changed

Some content is hidden

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

48 files changed

+575
-323
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1065,6 +1065,11 @@
10651065
"redirect_url": "/azure/container-instances/container-instances-resource-and-quota-limits",
10661066
"redirect_document_id": false
10671067
},
1068+
{
1069+
"source_path_from_root": "/articles/container-instances/container-instances-region-availability.md",
1070+
"redirect_url": "/azure/container-instances/container-instances-resource-and-quota-limits",
1071+
"redirect_document_id": false
1072+
},
10681073
{
10691074
"source_path_from_root": "/articles/cassandra-managed-instance/compare-cosmosdb-managed-instance.md",
10701075
"redirect_url": "/azure/managed-instance-apache-cassandra/compare-cosmosdb-managed-instance",

articles/azure-functions/functions-bindings-event-hubs-output.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ This article supports both programming models.
4545

4646
The following example shows a [C# function](dotnet-isolated-process-guide.md) that writes a message string to an event hub, using the method return value as the output:
4747

48-
:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/EventHubs/EventHubsFunction.cs" range="12-23":::
48+
:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/EventHubs/EventHubsFunction.cs" range="20-31":::
4949

5050
# [In-process model](#tab/in-process)
5151

articles/azure-monitor/best-practices-cost.md

Lines changed: 0 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -53,40 +53,6 @@ This article describes [Cost optimization](/azure/architecture/framework/cost/)
5353

5454
[!INCLUDE [waf-application-insights-cost](includes/waf-application-insights-cost.md)]
5555

56-
## Frequently asked questions
57-
58-
This section provides answers to common questions.
59-
60-
### Is Application Insights free?
61-
62-
Yes, for experimental use. In the basic pricing plan, your application can send a certain allowance of data each month free of charge. The free allowance is large enough to cover development and publishing an app for a few users. You can set a cap to prevent more than a specified amount of data from being processed.
63-
64-
Larger volumes of telemetry are charged per gigabyte. We provide some tips on how to [limit your charges](#application-insights).
65-
66-
The Enterprise plan incurs a charge for each day that each web server node sends telemetry. It's suitable if you want to use Continuous Export on a large scale.
67-
68-
Read the [pricing plan](https://azure.microsoft.com/pricing/details/application-insights/).
69-
70-
### How much does Application Insights cost?
71-
72-
* Open the **Usage and estimated costs** page in an Application Insights resource. There's a chart of recent usage. You can set a data volume cap, if you want.
73-
* To see your bills across all resources:
74-
75-
1. Open the [Azure portal](https://portal.azure.com).
76-
1. Search for **Cost Management** and use the **Cost analysis** pane to see forecasted costs.
77-
1. Search for **Cost Management and Billing** and open the **Billing scopes** pane to see current charges across subscriptions.
78-
79-
### Are there data transfer charges between an Azure web app and Application Insights?
80-
81-
* If your Azure web app is hosted in a datacenter where there's an Application Insights collection endpoint, there's no charge.
82-
* If there's no collection endpoint in your host datacenter, your app's telemetry incurs [Azure outgoing charges](https://azure.microsoft.com/pricing/details/bandwidth/).
83-
84-
This answer depends on the distribution of our endpoints, *not* on where your Application Insights resource is hosted.
85-
86-
### Do I incur network costs if my Application Insights resource is monitoring an Azure resource (that is, telemetry producer) in a different region?
87-
88-
Yes, you may incur more network costs, which vary depending on the region the telemetry is coming from and where it's going. Refer to [Azure bandwidth pricing](https://azure.microsoft.com/pricing/details/bandwidth/) for details.
89-
9056
## Next step
9157

9258
- [Get best practices for a complete deployment of Azure Monitor](best-practices.md).

articles/azure-monitor/data-sources.md

Lines changed: 32 additions & 32 deletions
Large diffs are not rendered by default.

articles/backup/backup-azure-arm-userestapi-createorupdatevault.md

Lines changed: 16 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,25 @@
11
---
2-
title: Create Recovery Services vaults using REST API
2+
title: Create Recovery Services vaults using REST API for Azure Backup
33
description: In this article, learn how to manage backup and restore operations of Azure VM Backup using REST API.
4-
ms.topic: conceptual
5-
ms.date: 08/21/2018
4+
ms.service: backup
5+
ms.topic: how-to
6+
ms.date: 04/09/2024
67
ms.assetid: e54750b4-4518-4262-8f23-ca2f0c7c0439
78
author: AbhishekMallick-MS
89
ms.author: v-abhmallick
10+
ms.custom: engagement-fy24
911
---
10-
# Create Azure Recovery Services vault using REST API
12+
# Create Azure Recovery Services vault using REST API for Azure Backup
1113

12-
The steps to create an Azure Recovery Services vault using REST API are outlined in [create vault REST API](/rest/api/recoveryservices/vaults/createorupdate) documentation. Let's use this document as a reference to create a vault called "testVault" in "West US".
14+
This article describes how to create Azure Recovery Services vault using REST API. To create the vault using the Azure portal, see [this article](backup-create-recovery-services-vault.md#create-a-recovery-services-vault).
1315

14-
To create or update an Azure Recovery Services vault, use the following *PUT* operation.
16+
A Recovery Services vault is a storage entity in Azure that houses data. The data is typically copies of data, or configuration information for virtual machines (VMs), workloads, servers, or workstations. You can use Recovery Services vaults to hold backup data for various Azure services such as IaaS VMs (Linux or Windows) and SQL Server in Azure VMs. Recovery Services vaults support System Center DPM, Windows Server, Azure Backup Server, and more. Recovery Services vaults make it easy to organize your backup data, while minimizing management overhead.
17+
18+
## Before you start
19+
20+
The creation of an Azure Recovery Services vault using REST API is outlined in [create vault REST API](/rest/api/recoveryservices/vaults/createorupdate) article. Let's use this article as a reference to create a vault named `testVault` in `West US`.
21+
22+
To create or update an Azure Recovery Services vault, use the following *PUT* operation:
1523

1624
```http
1725
PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}?api-version=2016-06-01
@@ -46,7 +54,7 @@ Note that vault name and resource group name are provided in the PUT URI. The re
4654

4755
## Example request body
4856

49-
The following example body is used to create a vault in "West US". Specify the location. The SKU is always "Standard".
57+
The following example body is used to create a vault in `West US`. Specify the location. The SKU is always `Standard`.
5058

5159
```json
5260
{
@@ -71,7 +79,7 @@ For more information about REST API responses, see [Process the response message
7179

7280
### Example response
7381

74-
A condensed *201 Created* response from the previous example request body shows an *id* has been assigned and the *provisioningState* is *Succeeded*:
82+
A condensed *201 Created* response from the previous example request body shows an *ID* has been assigned and the *provisioningState* is *Succeeded*:
7583

7684
```json
7785
{

articles/backup/backup-azure-arm-userestapi-managejobs.md

Lines changed: 15 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,20 @@
11
---
2-
title: Manage Backup Jobs using REST API
3-
description: In this article, learn how to track and manage backup and restore jobs of Azure Backup using REST API.
4-
ms.topic: conceptual
5-
ms.date: 08/03/2018
2+
title: Manage the backup jobs using REST API in Azure Backup
3+
description: In this article, learn how to track and manage the backup and restore jobs of Azure Backup using REST API.
4+
ms.service: backup
5+
ms.topic: how-to
6+
ms.date: 04/09/2024
67
ms.assetid: b234533e-ac51-4482-9452-d97444f98b38
78
author: AbhishekMallick-MS
89
ms.author: v-abhmallick
10+
ms.custom: engagement-fy24
911
---
1012

11-
# Track backup and restore jobs using REST API
13+
# Track the backup and restore jobs using REST API in Azure Backup
1214

13-
Azure Backup service triggers jobs that run in background in various scenarios such as triggering backup, restore operations, disabling backup. These jobs can be tracked using their IDs.
15+
This article describes how to monitor the backup and restore jobs using REST API in Azure Backup.
16+
17+
The Azure Backup service triggers jobs that run in background in various scenarios such as triggering backup, restore operations, disabling backup. You can track these jobs using their IDs.
1418

1519
## Fetch Job information from operations
1620

@@ -38,7 +42,7 @@ The Azure VM backup job is identified by "jobId" field and can be tracked as men
3842
GET https://management.azure.com/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupJobs/{jobName}?api-version=2019-05-13
3943
```
4044

41-
The `{jobName}` is "jobId" mentioned above. The response is always 200 OK with the "status" field indicating the current status of the job. Once it's "Completed" or "CompletedWithWarnings", the 'extendedInfo' section reveals more details about the job.
45+
The `{jobName}` is "jobId" mentioned above. The response is always 200 OK with the "status" field indicating the current status of the job. Once it's *Completed* or *CompletedWithWarnings*, the 'extendedInfo' section reveals more details about the job.
4246

4347
### Response
4448

@@ -48,7 +52,7 @@ The `{jobName}` is "jobId" mentioned above. The response is always 200 OK with t
4852

4953
#### Example response
5054

51-
Once the *GET* URI is submitted, a 200 (OK) response is returned.
55+
Once the *GET* URI submission is complete, a 200 (OK) response is returned.
5256

5357
```http
5458
HTTP/1.1 200 OK
@@ -106,3 +110,6 @@ X-Powered-By: ASP.NET
106110
}
107111
108112
```
113+
## Next steps
114+
115+
[About Azure Backup](backup-overview.md).

articles/container-instances/container-instances-region-availability.md

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

articles/cosmos-db/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
href: introduction.md
88
- name: FAQ
99
href: faq.yml
10-
- name: 30-day free trial
10+
- name: Try Azure Cosmos DB free
1111
href: try-free.md
1212
- name: Azure AI Advantage free trial
1313
href: ai-advantage.md
-4.66 KB
Loading

0 commit comments

Comments
 (0)