You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You're now done with the Azure Automation setup. You can test the webhooks with a simple Postman test to validate that the webhook works. Next, you must create the Logic App for orchestration.
84
+
You're now done with the Azure Automation setup. You can test the webhooks with a simple API test to validate that the webhook works. Some popular ways to query the API are:
Next, you must create the Logic App for orchestration.
85
93
86
94
## Create an Azure Logic App for orchestration
87
95
@@ -258,22 +266,27 @@ You can create a budget in the Azure portal using the [Budget feature](../costs/
258
266
259
267
### Create the Budget
260
268
261
-
Next, you'll configure **Postman** to create a budget by calling the Azure Consumption REST APIs. Postman is an API Development environment. You'll import environment and collection files into Postman. The collection contains grouped definitions of HTTP requests that call Azure Consumption REST APIs. The environment file contains variables that are used by the collection.
269
+
Next, you create a budget by calling the Azure Consumption REST APIs. You need a way to interact with APIs. Some popular ways to query the API are:
You import environment and collection files into your API client. The collection contains grouped definitions of HTTP requests that call Azure Consumption REST APIs. The environment file contains variables that are used by the collection.
262
278
263
-
1. Download and open the [Postman REST client](https://www.getpostman.com/) to execute the REST APIs.
264
-
1. In Postman, create a new request.
265
-
:::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-27.png" alt-text="Screenshot showing create a new request in Postman.":::
266
-
1. Save the new request as a collection, so that the new request has nothing on it.
267
-
:::image type="content" border="true" source="./media/cost-management-budget-scenario/billing-cost-management-budget-scenario-28.png" alt-text="Screenshot showing save the new request in Postman.":::
279
+
1. In your API client, create a new request.
280
+
1. Save the new request so that it has nothing in it.
268
281
1. Change the request from a `Get` to a `Put` action.
269
282
1. Modify the following URL by replacing `{subscriptionId}` with the **Subscription ID** that you used in the previous section of this tutorial. Also, modify the URL to include "SampleBudget" as the value for `{budgetName}`:
1. Set the **Value** to the token that was created using the ArmClient at the end of the last section.
274
-
1. Select **Body** tab within Postman.
275
-
1. Select the **raw**button option.
276
-
1. In the textbox, paste in the below sample budget definition, however you must replace the `subscriptionID`, `resourcegroupname`, and `actiongroupname` parameters with your subscription ID, a unique name for your resource group, and the action group name you created in both the URL and the request body:
287
+
1. Select Body in your API client.
288
+
1. Select the **raw** option in your API client.
289
+
1. In the text area in your API client, paste the following sample budget definition. You must replace the `subscriptionID`, `resourcegroupname`, and `actiongroupname` parameters with your subscription ID, a unique name for your resource group, and the action group name you created in both the URL and the request body:
277
290
278
291
```
279
292
{
@@ -308,7 +321,7 @@ Next, you'll configure **Postman** to create a budget by calling the Azure Consu
308
321
}
309
322
}
310
323
```
311
-
1. Press **Send** to send the request.
324
+
1. Send the request.
312
325
313
326
You now have all the pieces you need to call the [budgets API](/rest/api/consumption/budgets). The budgets API reference has more details on the specific requests, including:
Copy file name to clipboardExpand all lines: articles/cost-management-billing/reservations/prepay-hana-large-instances-reserved-capacity.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -254,5 +254,4 @@ location. You can also go to https://aka.ms/corequotaincrease to learn about quo
254
254
255
255
## Next steps
256
256
257
-
- Learn about [How to call Azure REST APIs with Postman and cURL](/rest/api/azure/#how-to-call-azure-rest-apis-with-postman).
258
257
- See [SKUs for SAP HANA on Azure (Large Instances)](../../virtual-machines/workloads/sap/hana-available-skus.md) for the available SKU list and regions.
0 commit comments