Skip to content

Commit f02dedb

Browse files
authored
Merge pull request #279534 from MicrosoftDocs/main
6/27/2024 PM Publish
2 parents 7ba675c + c025196 commit f02dedb

File tree

103 files changed

+2023
-1172
lines changed

Some content is hidden

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

103 files changed

+2023
-1172
lines changed

.openpublishing.redirection.azure-monitor.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5509,6 +5509,11 @@
55095509
"redirect_url": "/azure/azure-monitor/logs/resource-manager-workspace",
55105510
"redirect_document_id": false
55115511
},
5512+
{
5513+
"source_path_from_root": "/articles/azure-monitor/logs/resource-manager-cluster.md",
5514+
"redirect_url": "/azure/azure-monitor/logs/logs-dedicated-clusters",
5515+
"redirect_document_id": false
5516+
},
55125517
{
55135518
"source_path_from_root": "/articles/azure-monitor/visualize/powerbi.md",
55145519
"redirect_url": "/azure/azure-monitor/logs/log-powerbi",

articles/ai-services/openai/how-to/provisioned-throughput-onboarding.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure OpenAI Service Provisioned Throughput Units (PTU) onboarding
33
description: Learn about provisioned throughput units onboarding and Azure OpenAI.
44
ms.service: azure-ai-openai
55
ms.topic: conceptual
6-
ms.date: 05/02/2024
6+
ms.date: 06/25/2024
77
manager: nitinme
88
author: mrbullwinkle
99
ms.author: mbullwin
@@ -44,11 +44,13 @@ The **Provisioned** option and the capacity planner are only available in certai
4444
|---|---|
4545
|Model | OpenAI model you plan to use. For example: GPT-4 |
4646
| Version | Version of the model you plan to use, for example 0614 |
47-
| Prompt tokens | Number of tokens in the prompt for each call |
48-
| Generation tokens | Number of tokens generated by the model on each call |
49-
| Peak calls per minute | Peak concurrent load to the endpoint measured in calls per minute|
47+
| Peak calls per min | The number of calls per minute that are expected to be sent to the model |
48+
| Tokens in prompt call | The number of tokens in the prompt for each call to the model. Calls with larger prompts will utilize more of the PTU deployment. Currently this calculator assumes a single prompt value so for workloads with wide variance, we recommend benchmarking your deployment on your traffic to determine the most accurate estimate of PTU needed for your deployment. |
49+
| Tokens in model response | The number of tokens generated from each call to the model. Calls with larger generation sizes will utilize more of the PTU deployment. Currently this calculator assumes a single prompt value so for workloads with wide variance, we recommend benchmarking your deployment on your traffic to determine the most accurate estimate of PTU needed for your deployment. |
5050

51-
After you fill in the required details, select **Calculate** to view the suggested PTU for your scenario.
51+
After you fill in the required details, select **Calculate** button in the output column.
52+
53+
The values in the output column are the estimated value of PTU units required for the provided workload inputs. The first output value represents the estimated PTU units required for the workload, rounded to the nearest PTU scale increment. The second output value represents the raw estimated PTU units required for the workload. The token totals are calculated using the following equation: `Total = Peak calls per minute * (Tokens in prompt call + Tokens in model response)`.
5254

5355
:::image type="content" source="../media/how-to/provisioned-onboarding/capacity-calculator.png" alt-text="Screenshot of the Azure OpenAI Studio landing page." lightbox="../media/how-to/provisioned-onboarding/capacity-calculator.png":::
5456

26.1 KB
Loading

articles/aks/eks-edw-deploy.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ In this article, you will deploy an [AWS EDW workload][eks-edw-overview] to Azur
3535
3636
You use the `deploy.sh` script in the `deployment` directory of the [GitHub repository][github-repo] to deploy the application to Azure.
3737
38-
The script first checks that all of the [prerequisite tools][prerequisites] are installed. If not, the script terminates and displays an error message letting you know which prerequisites are missing. If this happens, review the prerequisites, install any missing tools, and then run the script again. You need [Node autoprovisioning (NAP) for AKS] feature flag registered on your Azure subscription. If it isn't already registered, the script executes an Azure CLI command to register the feature flag.
38+
The script first checks that all of the [prerequisite tools][prerequisites] are installed. If not, the script terminates and displays an error message letting you know which prerequisites are missing. If this happens, review the prerequisites, install any missing tools, and then run the script again. The [Node autoprovisioning (NAP) for AKS][nap-aks] feature flag must be registered on your Azure subscription. If it isn't already registered, the script executes an Azure CLI command to register the feature flag.
3939
4040
The script records the state of the deployment in a file called `deploy.state`, which is located in the `deployment` directory. You can use this file to set environment variables when deploying the app.
4141
@@ -304,3 +304,4 @@ For more information on developing and running applications in AKS, see the foll
304304
[helm-aks]: ./kubernetes-helm.md
305305
[k8s-aks]: ./deploy-marketplace.md
306306
[openai-aks]: ./open-ai-quickstart.md
307+
[nap-aks]: ./node-autoprovision.md
16.8 KB
Loading
-30.5 KB
Loading

articles/application-gateway/certificates-for-backend-authentication.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: application-gateway
66
author: greg-lindsay
77
ms.service: application-gateway
88
ms.topic: how-to
9-
ms.date: 12/27/2022
9+
ms.date: 06/27/2024
1010
ms.author: greglin
1111
---
1212

@@ -32,40 +32,40 @@ From your TLS/SSL certificate, export the public key .cer file (not the private
3232

3333
1. To obtain a .cer file from the certificate, open **Manage user certificates**. Locate the certificate, typically in 'Certificates - Current User\Personal\Certificates', and right-click. Click **All Tasks**, and then click **Export**. This opens the **Certificate Export Wizard**. If you want to open Certificate Manager in current user scope using PowerShell, you type *certmgr* in the console window.
3434

35-
> [!NOTE]
36-
> If you can't find the certificate under Current User\Personal\Certificates, you may have accidentally opened "Certificates - Local Computer", rather than "Certificates - Current User").
35+
> [!NOTE]
36+
> If you can't find the certificate under Current User\Personal\Certificates, you may have accidentally opened "Certificates - Local Computer", rather than "Certificates - Current User").
3737
3838
![Screenshot shows the Certificate Manager with Certificates selected and a contextual menu with All tasks, then Export selected.](./media/certificates-for-backend-authentication/export.png)
3939

40-
1. In the Wizard, click **Next**.
40+
2. In the Wizard, click **Next**.
4141

4242
![Export certificate](./media/certificates-for-backend-authentication/exportwizard.png)
4343

44-
1. Select **No, do not export the private key**, and then click **Next**.
44+
3. Select **No, do not export the private key**, and then click **Next**.
4545

4646
![Do not export the private key](./media/certificates-for-backend-authentication/notprivatekey.png)
4747

48-
1. On the **Export File Format** page, select **Base-64 encoded X.509 (.CER).**, and then click **Next**.
48+
4. On the **Export File Format** page, select **Base-64 encoded X.509 (.CER).**, and then click **Next**.
4949

5050
![Base-64 encoded](./media/certificates-for-backend-authentication/base64.png)
5151

52-
1. For **File to Export**, **Browse** to the location to which you want to export the certificate. For **File name**, name the certificate file. Then, click **Next**.
52+
5. For **File to Export**, **Browse** to the location to which you want to export the certificate. For **File name**, name the certificate file. Then, click **Next**.
5353

5454
![Screenshot shows the Certificate Export Wizard where you specify a file to export.](./media/certificates-for-backend-authentication/browse.png)
5555

56-
1. Click **Finish** to export the certificate.
56+
6. Click **Finish** to export the certificate.
5757

5858
![Screenshot shows the Certificate Export Wizard after you complete the file export.](./media/certificates-for-backend-authentication/finish-screen.png)
5959

60-
1. Your certificate is successfully exported.
60+
7. Your certificate is successfully exported.
6161

6262
![Screenshot shows the Certificate Export Wizard with a success message.](./media/certificates-for-backend-authentication/success.png)
6363

6464
The exported certificate looks similar to this:
6565

6666
![Screenshot shows a certificate symbol.](./media/certificates-for-backend-authentication/exported.png)
6767

68-
1. If you open the exported certificate using Notepad, you see something similar to this example. The section in blue contains the information that is uploaded to application gateway. If you open your certificate with Notepad and it doesn't look similar to this, typically this means you didn't export it using the Base-64 encoded X.509(.CER) format. Additionally, if you want to use a different text editor, understand that some editors can introduce unintended formatting in the background. This can create problems when uploaded the text from this certificate to Azure.
68+
8. If you open the exported certificate using Notepad, you see something similar to this example. The section in blue contains the information that is uploaded to application gateway. If you open your certificate with Notepad and it doesn't look similar to this, typically this means you didn't export it using the Base-64 encoded X.509(.CER) format. Additionally, if you want to use a different text editor, understand that some editors can introduce unintended formatting in the background. This can create problems when uploaded the text from this certificate to Azure.
6969

7070
![Open with Notepad](./media/certificates-for-backend-authentication/format.png)
7171

articles/application-gateway/classic-to-resource-manager.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application-gateway
55
author: greg-lindsay
66
ms.service: application-gateway
77
ms.topic: how-to
8-
ms.date: 02/10/2022
8+
ms.date: 06/27/2024
99
ms.author: greglin
1010
---
1111

@@ -34,6 +34,9 @@ For more information on how to set up an Application Gateway resource after VNet
3434

3535
The word "classic" in classic networking service refers to networking resources managed by Azure Service Manager (ASM). Azure Service Manager (ASM) is the old control plane of Azure responsible for creating, managing, deleting VMs and performing other control plane operations.
3636

37+
> [!NOTE]
38+
> To view all the classic resources in your subscription, Open the **All Resources** blade and look for a **(Classic)** suffix after the resource name.
39+
3740
### What is Azure Resource Manager?
3841

3942
Azure Resource Manager is the latest control plane of Azure responsible for creating, managing, deleting VMs and performing other control plane operations.

articles/automation/automation-runbook-execution.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Runbook execution in Azure Automation
33
description: This article provides an overview of the processing of runbooks in Azure Automation.
44
services: automation
55
ms.subservice: process-automation
6-
ms.date: 12/28/2022
6+
ms.date: 06/27/2024
77
ms.topic: conceptual
88
ms.custom:
99
---
@@ -148,6 +148,7 @@ The following table describes the statuses that are possible for a job. You can
148148
| Stopping |The system is stopping the job. |
149149
| Suspended |Applies to [graphical and PowerShell Workflow runbooks](automation-runbook-types.md) only. The job was suspended by the user, by the system, or by a command in the runbook. If a runbook doesn't have a checkpoint, it starts from the beginning. If it has a checkpoint, it can start again and resume from its last checkpoint. The system only suspends the runbook when an exception occurs. By default, the `ErrorActionPreference` variable is set to Continue, indicating that the job keeps running on an error. If the preference variable is set to Stop, the job suspends on an error. |
150150
| Suspending |Applies to [graphical and PowerShell Workflow runbooks](automation-runbook-types.md) only. The system is trying to suspend the job at the request of the user. The runbook must reach its next checkpoint before it can be suspended. If it has already passed its last checkpoint, it completes before it can be suspended. |
151+
| New | The job has been submitted recently but is not yet activated.|
151152

152153
## Activity logging
153154

articles/automation/how-to/automation-region-dns-records.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Datacenter DNS records used by Azure Automation | Microsoft Docs
33
description: This article provides the DNS records required by Azure Automation features when restricting communication to a specific Azure region hosting that Automation account.
44
services: automation
55
ms.subservice: process-automation
6-
ms.date: 06/29/2021
6+
ms.date: 06/28/2024
77
ms.topic: conceptual
88
---
99

@@ -63,6 +63,7 @@ To support [Private Link](../../private-link/private-link-overview.md) in Azure
6363
| China East 2 |`https://<accountId>.webhook.sha2.azure-automation.cn`<br>`https://<accountId>.agentsvc.sha2.azure-automation.cn`<br>`https://<accountId>.jrds.sha2.azure-automation.cn` |
6464
| China North |`https://<accountId>.webhook.bjb.azure-automation.cn`<br>`https://<accountId>.agentsvc.bjb.azure-automation.cn`<br>`https://<accountId>.jrds.bjb.azure-automation.cn` |
6565
| China North 2 |`https://<accountId>.webhook.bjs2.azure-automation.cn`<br>`https://<accountId>.agentsvc.bjs2.azure-automation.cn`<br>`https://<accountId>.jrds.bjs2.azure-automation.cn` |
66+
| China North 3 | `https://<accountId>.webhook.cnn3.azure-automation.cn` </br> `https://<accountId>.agentsvc.cnn3.azure-automation.cn` </br> `https://<accountId>.jrds.cnn3.azure-automation.cn` |
6667
| West Europe |`https://<accountId>.webhook.we.azure-automation.net`<br>`https://<accountId>.agentsvc.we.azure-automation.net`<br>`https://<accountId>.jrds.we.azure-automation.net` |
6768
| North Europe |`https://<accountId>.webhook.ne.azure-automation.net`<br>`https://<accountId>.agentsvc.ne.azure-automation.net`<br>`https://<accountId>.jrds.ne.azure-automation.net` |
6869
| France Central |`https://<accountId>.webhook.fc.azure-automation.net`<br>`https://<accountId>.agentsvc.fc.azure-automation.net`<br>`https://<accountId>.jrds.fc.azure-automation.net` |

0 commit comments

Comments
 (0)