Skip to content

Commit 63b6ad3

Browse files
authored
Merge pull request #278802 from MicrosoftDocs/main
6/20/2024 AM Publish
2 parents a399137 + 0b5740a commit 63b6ad3

File tree

76 files changed

+2245
-380
lines changed

Some content is hidden

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

76 files changed

+2245
-380
lines changed

articles/ai-studio/concepts/retrieval-augmented-generation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,18 +22,18 @@ This article talks about the importance and need for Retrieval Augmented Generat
2222

2323
## What is RAG?
2424

25-
Some basics first. Large language models (LLMs) like ChatGPT are trained on public internet data which was available at the point in time when they were trained. They can answer questions related to the data they were trained on. This public data might not be sufficient to meet all your needs. You might want questions answered based on your private data. Or, the public data might simply have gotten out of date. The solution to this problem is Retrieval Augmented Generation (RAG), a pattern used in AI which uses an LLM to generate answers with your own data.
25+
Some basics first. Large language models (LLMs) like ChatGPT are trained on public internet data that was available at the point in time when they were trained. They can answer questions related to the data they were trained on. This public data might not be sufficient to meet all your needs. You might want questions answered based on your private data. Or, the public data might simply have gotten out of date. The solution to this problem is Retrieval Augmented Generation (RAG), a pattern used in AI that uses an LLM to generate answers with your own data.
2626

2727
## How does RAG work?
2828

29-
RAG is a pattern which uses your data with an LLM to generate answers specific to your data. When a user asks a question, the data store is searched based on user input. The user question is then combined with the matching results and sent to the LLM using a prompt (explicit instructions to an AI or machine learning model) to generate the desired answer. This can be illustrated as follows.
29+
RAG is a pattern that uses your data with an LLM to generate answers specific to your data. When a user asks a question, the data store is searched based on user input. The user question is then combined with the matching results and sent to the LLM using a prompt (explicit instructions to an AI or machine learning model) to generate the desired answer. This can be illustrated as follows.
3030

3131
:::image type="content" source="../media/index-retrieve/rag-pattern.png" alt-text="Screenshot of the RAG pattern." lightbox="../media/index-retrieve/rag-pattern.png":::
3232

3333

3434
## What is an index and why do I need it?
3535

36-
RAG uses your data to generate answers to the user question. For RAG to work well, we need to find a way to search and send your data in an easy and cost efficient manner to the LLMs. This is achieved by using an index. An index is a data store which allows you to search data efficiently. This is very useful in RAG. An index can be optimized for LLMs by creating vectors (text data converted to number sequences using an embedding model). A good index usually has efficient search capabilities like keyword searches, semantic searches, vector searches or a combination of these. This optimized RAG pattern can be illustrated as follows.
36+
RAG uses your data to generate answers to the user question. For RAG to work well, we need to find a way to search and send your data in an easy and cost efficient manner to the LLMs. This is achieved by using an index. An index is a data store that allows you to search data efficiently. This is very useful in RAG. An index can be optimized for LLMs by creating vectors (text data converted to number sequences using an embedding model). A good index usually has efficient search capabilities like keyword searches, semantic searches, vector searches or a combination of these. This optimized RAG pattern can be illustrated as follows.
3737

3838
:::image type="content" source="../media/index-retrieve/rag-pattern-with-index.png" alt-text="Screenshot of the RAG pattern with index." lightbox="../media/index-retrieve/rag-pattern-with-index.png":::
3939

2.46 KB
Loading
2.22 KB
Loading

articles/app-service/deploy-container-azure-pipelines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,10 +20,10 @@ In this article, we use Azure Pipelines to deploy a Windows container applicatio
2020
- A working Windows app with Dockerfile hosted on [Azure Repos](https://docs.github.com/get-started/quickstart/create-a-repo).
2121

2222
## Add a Service Connection
23-
Before you create your pipeline, you should first create your Service Connection since you'll be asked to choose and verify your connection when creating your template. A Service Connection allows you to connect to your registry of choice (ACR or Docker Hub) when using the task templates. When adding a new service connection, choose the Docker Registry option. The following form asks you to choose Docker Hub or Azure Container Registry along with pertaining information. To follow along with this tutorial, use Azure Container Registry. You can create a new Service Connection following the directions [here](https://learn.microsoft.com/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml#create-new).
23+
Before you create your pipeline, you should first create your Service Connection since you'll be asked to choose and verify your connection when creating your template. A Service Connection allows you to connect to your registry of choice (ACR or Docker Hub) when using the task templates. When adding a new service connection, choose the Docker Registry option. The following form asks you to choose Docker Hub or Azure Container Registry along with pertaining information. To follow along with this tutorial, use Azure Container Registry. You can create a new Service Connection following the directions [here](/azure/devops/pipelines/library/service-endpoints).
2424

2525
## Secure your secrets
26-
Since we're using sensitive information that you don't want others to access, we use variables to protect our information. Create a variable by following the directions [here](https://learn.microsoft.com/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#secret-variables).
26+
Since we're using sensitive information that you don't want others to access, we use variables to protect our information. Create a variable by following the directions [here](/azure/devops/pipelines/process/variables).
2727

2828
To add a Variable, you click the **Variables** button next to the Save button in the top-right of the editing view for your pipeline. Select the **New Variable** button and enter your information. Add the variables below with your own secrets appropriate from each resource.
2929

articles/app-service/environment/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
items:
55
- name: About App Service Environment
66
href: overview.md
7-
- name: App Service offering comparison
7+
- name: Compare with App Service
88
href: ase-multi-tenant-comparison.md
99
- name: Version comparison
1010
href: version-comparison.md
@@ -142,4 +142,4 @@
142142
- name: Open-source technologies FAQ
143143
href: ../faq-open-source-technologies.yml?toc=%2fazure%2fapp-service%2fenvironment%2ftoc.json
144144
- name: Configuration and management FAQ
145-
href: ../faq-configuration-and-management.yml?toc=%2fazure%2fapp-service%2fenvironment%2ftoc.json
145+
href: ../faq-configuration-and-management.yml?toc=%2fazure%2fapp-service%2fenvironment%2ftoc.json

articles/automation/automation-create-standalone-account.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ The following image shows a standard configuration for a new Automation account.
7373

7474
### Networking
7575

76-
On the **Networking** tab, you can configure connectivity to Automation Account - either publicly via public IP addresses or privately using a [Azure Automation Private Link](./how-to/private-link-security.md). Azure Automation Private Link connects one or more private endpoints (and therefore the virtual networks they are contained in) to your Automation Account resource.
76+
On the **Networking** tab, you can configure connectivity to Automation Account - either publicly via public IP addresses or privately using an [Azure Automation Private Link](./how-to/private-link-security.md). Azure Automation Private Link connects one or more private endpoints (and therefore the virtual networks they are contained in) to your Automation Account resource.
7777

7878
The following image shows a standard configuration for a new Automation account.
7979

articles/azure-arc/servers/agent-release-notes.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: What's new with Azure Connected Machine agent
33
description: This article has release notes for Azure Connected Machine agent. For many of the summarized issues, there are links to more details.
44
ms.topic: overview
5-
ms.date: 04/09/2024
5+
ms.date: 06/19/2024
66
ms.custom: references_regions
77
---
88

@@ -20,6 +20,16 @@ This page is updated monthly, so revisit it regularly. If you're looking for ite
2020
> Only Connected Machine agent versions within the last 1 year are officially supported by the product group. Customers should update to an agent version within this window.
2121
>
2222
23+
## Version 1.43 - June 2024
24+
25+
Download for [Windows](https://aka.ms/AzureConnectedMachineAgent) or [Linux](manage-agent.md#installing-a-specific-version-of-the-agent)
26+
27+
### Fixed
28+
29+
- Fix for OpenSSL Vulnerability for Linux (Upgrading OpenSSL version from 3.0.13 to 3.014)
30+
- Added Server Name Indicator (SNI) to our service calls, fixing Proxy and Firewall scenarios
31+
- Skipped lockdown policy on the downloads directory under Guest Configuration
32+
2333
## Version 1.42 - May 2024 (Second Release)
2434

2535
Download for [Windows](https://download.microsoft.com/download/9/6/0/9600825a-e532-4e50-a2d5-7f07e400afc1/AzureConnectedMachineAgent.msi) or [Linux](manage-agent.md#installing-a-specific-version-of-the-agent)

articles/azure-monitor/alerts/action-groups.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -561,7 +561,7 @@ If you use the webhook action, your target webhook endpoint must be able to proc
561561

562562
> [!NOTE]
563563
>
564-
>Pre-requisites: https://learn.microsoft.com/powershell/microsoftgraph/installation?view=graph-powershell-1.0
564+
>Pre-requisites: [Install the Microsoft Graph PowerShell SDK](/powershell/microsoftgraph/installation?view=graph-powershell-1.0&preserve-view=true)
565565
566566
#### How to run?
567567

articles/azure-monitor/essentials/create-diagnostic-settings.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -90,12 +90,10 @@ Use the [New-AzDiagnosticSetting](/powershell/module/az.monitor/new-azdiagnostic
9090
The following example PowerShell cmdlet creates a diagnostic setting for all logs, or for audit logs, and metrics for a key vault by using Log Analytics Workspace.
9191

9292
```powershell
93-
$KV= Get-AzKeyVault -ResourceGroupName <resource group name> -VaultName <key vault name>
94-
$Law= Get-AzOperationalInsightsWorkspace -ResourceGroupName <resource group name> -Name <workspace name> #LAW name is case sensitive
93+
$KV = Get-AzKeyVault -ResourceGroupName <resource group name> -VaultName <key vault name>
94+
$Law = Get-AzOperationalInsightsWorkspace -ResourceGroupName <resource group name> -Name <workspace name> # LAW name is case sensitive
9595
96-
$metric = @()
97-
$log = @()
98-
$metric += New-AzDiagnosticSettingMetricSettingsObject -Enabled $true -Category AllMetrics
96+
$metric = New-AzDiagnosticSettingMetricSettingsObject -Enabled $true -Category AllMetrics
9997
# For all available logs, use:
10098
$log = New-AzDiagnosticSettingLogSettingsObject -Enabled $true -CategoryGroup allLogs
10199
# or, for audit logs, use:

articles/azure-monitor/essentials/data-collection-endpoint-overview.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,7 @@ This table describes the components of a data collection endpoint, related regio
3535
| Component | Description | Regionality considerations |Data collection rule configuration |
3636
|:---|:---|:---|:---|
3737
| Logs ingestion endpoint | The endpoint that ingests logs into the data ingestion pipeline. Azure Monitor transforms the data and sends it to the defined destination Log Analytics workspace and table based on a DCR ID sent with the collected data.<br>Example: `<unique-dce-identifier>.<regionname>-1.ingest`. |Same region as the destination Log Analytics workspace. |Set on the **Basics** tab when you create a data collection rule using the portal. |
38+
| Metrics ingestion endpoint | The endpoint that ingests metrics into the data ingestion pipeline. Azure Monitor transforms the data and sends it to the defined destination Azure Monitor workspace and table based on a DCR ID sent with the collected data.<br>Example: `<unique-dce-identifier>.<regionname>-1.metrics.ingest`. |Same region as the destination Azure Monitor workspace. |Set on the **Basics** tab when you create a data collection rule using the portal. |
3839
| Configuration access endpoint | The endpoint from which Azure Monitor Agent retrieves data collection rules (DCRs).<br>Example: `<unique-dce-identifier>.<regionname>-1.handler.control`. | Same region as the monitored resources. | Set on the **Resources** tab when you create a data collection rule using the portal.|
3940

4041

@@ -109,6 +110,9 @@ The sample data collection endpoint (DCE) below is for virtual machines with Azu
109110
"logsIngestion": {
110111
"endpoint": "https://mycollectionendpoint-abcd.eastus-1.ingest.monitor.azure.com"
111112
},
113+
"metricsIngestion": {
114+
"endpoint": "https://mycollectionendpoint-abcd.eastus-1.metrics.ingest.monitor.azure.com"
115+
},
112116
"networkAcls": {
113117
"publicNetworkAccess": "Disabled"
114118
}
@@ -127,7 +131,7 @@ The sample data collection endpoint (DCE) below is for virtual machines with Azu
127131

128132
## Limitations
129133

130-
- Data collection endpoints only support Log Analytics workspaces as a destination for collected data. [Custom metrics (preview)](../essentials/metrics-custom-overview.md) collected and uploaded via Azure Monitor Agent aren't currently controlled by DCEs.
134+
- Data collection endpoints only support Log Analytics workspaces and Azure Monitor Workspace as destinations for collected data. [Custom metrics (preview)](../essentials/metrics-custom-overview.md) collected and uploaded via Azure Monitor Agent aren't currently controlled by DCEs.
131135

132136

133137
## Next steps

0 commit comments

Comments
 (0)