Skip to content

Commit 971f020

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into tamram-251126
2 parents 7f8a955 + 698fe9b commit 971f020

File tree

78 files changed

+609
-165
lines changed

Some content is hidden

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

78 files changed

+609
-165
lines changed

articles/ai-services/language-service/question-answering/how-to/azure-openai-integration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,4 +74,4 @@ At the same time, customers often require a custom answer authoring experience t
7474
You can now start exploring Azure OpenAI capabilities with a no-code approach through the chat playground. It's simply a text box where you can submit a prompt to generate a completion. From this page, you can quickly iterate and experiment with the capabilities. You can also launch a [web app](../../../openai/how-to/use-web-app.md) to chat with the model over the web.
7575

7676
## Next steps
77-
* [Using Azure OpenAI on your data](../../../openai/concepts/use-your-data.md)
77+
* [Using Azure OpenAI on your data](../../../openai/concepts/use-your-data.md)

articles/ai-services/language-service/question-answering/overview.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ ms.custom: language-service-question-answering
1313

1414
# What is custom question answering?
1515

16+
> [!NOTE]
17+
> [Azure Open AI On Your Data](../../openai/concepts/use-your-data.md) utilizes large language models (LLMs) to produce similar results to Custom Question Answering. If you wish to connect an existing Custom Question Answering project to Azure Open AI On Your Data, please check out our [guide]( how-to/azure-openai-integration.md).
18+
1619
Custom question answering provides cloud-based Natural Language Processing (NLP) that allows you to create a natural conversational layer over your data. It is used to find appropriate answers from customer input or from a project.
1720

1821
Custom question answering is commonly used to build conversational client applications, which include social media applications, chat bots, and speech-enabled desktop applications. This offering includes features like enhanced relevance using a deep learning ranker, precise answers, and end-to-end region support.

articles/ai-services/language-service/question-answering/quickstart/sdk.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@ zone_pivot_groups: custom-qna-quickstart
1515

1616
# Quickstart: custom question answering
1717

18+
> [!NOTE]
19+
> [Azure Open AI On Your Data](../../../openai/concepts/use-your-data.md) utilizes large language models (LLMs) to produce similar results to Custom Question Answering. If you wish to connect an existing Custom Question Answering project to Azure Open AI On Your Data, please check out our [guide](../how-to/azure-openai-integration.md).
20+
1821
> [!NOTE]
1922
> Are you looking to migrate your workloads from QnA Maker? See our [migration guide](../how-to/migrate-qnamaker-to-question-answering.md) for information on feature comparisons and migration steps.
2023

articles/ai-services/qnamaker/Overview/overview.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ keywords: "qna maker, low code chat bots, multi-turn conversations"
1313

1414
# What is QnA Maker?
1515

16+
> [!NOTE]
17+
> [Azure Open AI On Your Data](../../openai/concepts/use-your-data.md) utilizes large language models (LLMs) to produce similar results to QnA Maker. If you wish to migrate your QnA Maker project to Azure Open AI On Your Data, please check out our [guide](../How-To/migrate-to-openai.md).
18+
1619
[!INCLUDE [Custom question answering](../includes/new-version.md)]
1720

1821
[!INCLUDE [Azure AI services rebrand](../../includes/rebrand-note.md)]

articles/ai-services/qnamaker/Quickstarts/add-question-metadata-portal.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ ms.custom: mode-ui
1313

1414
# Add questions and answer with QnA Maker portal
1515

16+
> [!NOTE]
17+
> [Azure Open AI On Your Data](../../openai/concepts/use-your-data.md) utilizes large language models (LLMs) to produce similar results to QnA Maker. If you wish to migrate your QnA Maker project to Azure Open AI On Your Data, please check out our [guide](../How-To/migrate-to-openai.md).
18+
1619
Once a knowledge base is created, add question and answer (QnA) pairs with metadata to filter the answer. The questions in the following table are about Azure service limits, but each has to do with a different Azure search service.
1720

1821
[!INCLUDE [Custom question answering](../includes/new-version.md)]

articles/ai-services/qnamaker/Quickstarts/create-publish-knowledge-base.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ ms.custom: mode-other
1313

1414
# Quickstart: Create, train, and publish your QnA Maker knowledge base
1515

16+
> [!NOTE]
17+
> [Azure Open AI On Your Data](../../openai/concepts/use-your-data.md) utilizes large language models (LLMs) to produce similar results to QnA Maker. If you wish to migrate your QnA Maker project to Azure Open AI On Your Data, please check out our [guide](../How-To/migrate-to-openai.md).
18+
1619
[!INCLUDE [Custom question answering](../includes/new-version.md)]
1720

1821
You can create a QnA Maker knowledge base (KB) from your own content, such as FAQs or product manuals. This article includes an example of creating a QnA Maker knowledge base from a simple FAQ webpage, to answer questions.

articles/ai-services/qnamaker/Quickstarts/get-answer-from-knowledge-base-using-url-tool.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@ ms.date: 01/19/2024
1515

1616
# Get an answer from a QNA Maker knowledge base
1717

18+
> [!NOTE]
19+
> [Azure Open AI On Your Data](../../openai/concepts/use-your-data.md) utilizes large language models (LLMs) to produce similar results to QnA Maker. If you wish to migrate your QnA Maker project to Azure Open AI On Your Data, please check out our [guide](../How-To/migrate-to-openai.md).
20+
1821
[!INCLUDE [Custom question answering](../includes/new-version.md)]
1922

2023
> [!NOTE]

articles/ai-services/qnamaker/Quickstarts/quickstart-sdk.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@ zone_pivot_groups: qnamaker-quickstart
1515

1616
# Quickstart: QnA Maker client library
1717

18+
> [!NOTE]
19+
> [Azure Open AI On Your Data](../../openai/concepts/use-your-data.md) utilizes large language models (LLMs) to produce similar results to QnA Maker. If you wish to migrate your QnA Maker project to Azure Open AI On Your Data, please check out our [guide](../How-To/migrate-to-openai.md).
20+
1821
Get started with the QnA Maker client library. Follow these steps to install the package and try out the example code for basic tasks.
1922

2023
[!INCLUDE [Custom question answering](../includes/new-version.md)]

articles/application-gateway/ipv6-application-gateway-portal.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.custom: mvc, mode-ui
1414
# Configure Application Gateway with a frontend public IPv6 address using the Azure portal
1515

1616
> [!IMPORTANT]
17-
> Application Gateway IPv6 support is now generally available. Updates to the Azure portal for IPv6 support are currently being deployed across all regions and will be fully available within the next few weeks. In the meantime to use the portal to create an IPv6 Application Gateway continue using the [preview registration process](/azure/azure-resource-manager/management/preview-features?tabs=azure-portal) in the Azure portal to opt in for **Allow Application Gateway IPv6 Access**.
17+
> Application Gateway IPv6 support is now generally available.
1818
1919
[Azure Application Gateway](overview.md) supports dual stack (IPv4 and IPv6) frontend connections from clients. To use IPv6 frontend connectivity, you need to create a new Application Gateway. Currently you can’t upgrade existing IPv4 only Application Gateways to dual stack (IPv4 and IPv6) Application Gateways. Also, currently backend IPv6 addresses aren't supported.
2020

@@ -37,7 +37,7 @@ You can also complete this quickstart using [Azure PowerShell](ipv6-application-
3737

3838
## Regions and availability
3939

40-
The IPv6 Application Gateway preview is available to all public cloud regions where Application Gateway v2 SKU is supported. It's also available in [Microsoft Azure operated by 21Vianet](https://www.azure.cn/) and [Azure Government](https://azure.microsoft.com/overview/clouds/government/)
40+
The IPv6 Application Gateway is available to all public cloud regions where Application Gateway v2 SKU is supported. It's also available in [Microsoft Azure operated by 21Vianet](https://www.azure.cn/) and [Azure Government](https://azure.microsoft.com/overview/clouds/government/)
4141

4242
## Limitations
4343

@@ -56,7 +56,7 @@ An Azure account with an active subscription is required. If you don't already
5656

5757
Sign in to the [Azure portal](https://portal.azure.com) with your Azure account.
5858

59-
Use the [preview registration process](/azure/azure-resource-manager/management/preview-features?tabs=azure-portal) in the Azure portal to **Allow Application Gateway IPv6 Access**. This is required until the feature is completely rolled out in the Azure portal.
59+
6060

6161
## Create an application gateway
6262

@@ -103,14 +103,14 @@ Create the application gateway using the tabs on the **Create application gatewa
103103
1. On the **Frontends** tab, verify **Frontend IP address type** is set to **Public**.
104104

105105
> [!IMPORTANT]
106-
> For the Application Gateway v2 SKU, there must be a **Public** frontend IP configuration. A private IPv6 frontend IP configuration (Only ILB mode) is currently not supported for the IPv6 Application Gateway preview.
106+
> For the Application Gateway v2 SKU, there must be a **Public** frontend IP configuration. A private IPv6 frontend IP configuration (Only ILB mode) is currently not supported for the IPv6 Application Gateway.
107107
108108
2. Select **Add new** for the **Public IP address**, enter a name for the public IP address, and select **OK**. For example, **myAGPublicIPAddress**.
109109

110110
![A screenshot of create new application gateway: frontends.](./media/ipv6-application-gateway-portal/ipv6-frontends.png)
111111

112112
> [!NOTE]
113-
> IPv6 Application Gateway (preview) supports up to 4 frontend IP addresses: two IPv4 addresses (Public and Private) and two IPv6 addresses (Public and Private)
113+
> IPv6 Application Gateway supports up to 4 frontend IP addresses: two IPv4 addresses (Public and Private) and two IPv6 addresses (Public and Private)
114114
115115

116116
3. Select **Next: Backends**.

articles/azure-cache-for-redis/cache-managed-identity.md

Lines changed: 11 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -25,13 +25,9 @@ Presently, Azure Cache for Redis can use a managed identity to connect with a st
2525

2626
Managed identity lets you simplify the process of securely connecting to your chosen storage account for these tasks.
2727

28-
> [!NOTE]
29-
> This functionality does not yet support authentication for connecting to a cache instance.
30-
>
31-
3228
Azure Cache for Redis supports [both types of managed identity](../active-directory/managed-identities-azure-resources/overview.md):
3329

34-
- **System-assigned identity** is specific to the resource. In this case, the cache is the resource. When the cache is deleted, the identity is deleted.
30+
- **System-assigned identity** is specific to the resource. In this case, the cache is the resource. When the cache is deleted, the identity is deleted.
3531

3632
- **User-assigned identity** is specific to a user, not the resource. It can be assigned to any resource that supports managed identity and remains even when you delete the cache.
3733

@@ -130,23 +126,23 @@ Set-AzRedisCache -ResourceGroupName \"MyGroup\" -Name \"MyCache\" -IdentityType
130126
131127
1. Create a new storage account or open an existing storage account that you would like to connect to your cache instance.
132128

133-
2. Open the **Access control (IAM)** from the Resource menu. Then, select **Add**, and **Add role assignment**.
129+
1. Open the **Access control (IAM)** from the Resource menu. Then, select **Add**, and **Add role assignment**.
134130

135131
:::image type="content" source="media/cache-managed-identity/demo-storage.png" alt-text="Screenshot showing the Access Control (IAM) settings.":::
136132

137-
3. Search for the **Storage Blob Data Contributor** on the Role pane. Select it and **Next**.
133+
1. Search for the **Storage Blob Data Contributor** on the Role pane. Select it and **Next**.
138134

139135
:::image type="content" source="media/cache-managed-identity/role-assignment.png" alt-text="Screenshot showing Add role assignment form with list of roles.":::
140136

141-
4. Select the **Members** tab. Under **Assign access to** select **Managed Identity**, and select on **Select members**. A sidebar pops up next to the working pane.
137+
1. Select the **Members** tab. Under **Assign access to** select **Managed Identity**, and select on **Select members**. A sidebar pops up next to the working pane.
142138

143139
:::image type="content" source="media/cache-managed-identity/select-members.png" alt-text="Screenshot showing add role assignment form with members pane.":::
144140

145-
5. Use the drop-down under **Managed Identity** to choose either a **User-assigned managed identity** or a **System-assigned managed identity**. If you have many managed identities, you can search by name. Choose the managed identities you want and then **Select**. Then, **Review + assign** to confirm.
141+
1. Use the drop-down under **Managed Identity** to choose either a **User-assigned managed identity** or a **System-assigned managed identity**. If you have many managed identities, you can search by name. Choose the managed identities you want and then **Select**. Then, **Review + assign** to confirm.
146142

147143
:::image type="content" source="media/cache-managed-identity/review-assign.png" alt-text="Screenshot showing Managed Identity form with User-assigned managed identity indicated.":::
148144

149-
6. You can confirm if the identity has been assigned successfully by checking your storage account's role assignments under **Storage Blob Data Contributor**.
145+
1. You can confirm if the identity has been assigned successfully by checking your storage account's role assignments under **Storage Blob Data Contributor**.
150146

151147
:::image type="content" source="media/cache-managed-identity/blob-data.png" alt-text="Screenshot of Storage Blob Data Contributor list.":::
152148

@@ -155,7 +151,6 @@ Set-AzRedisCache -ResourceGroupName \"MyGroup\" -Name \"MyCache\" -IdentityType
155151
>- add an Azure Cache for Redis instance as a storage blob data contributor through system-assigned identity, and
156152
>- check [**Allow Azure services on the trusted services list to access this storage account**](../storage/common/storage-network-security.md?tabs=azure-portal#grant-access-to-trusted-azure-services).
157153
158-
159154
If you're not using managed identity and instead authorizing a storage account with a key, then having firewall exceptions on the storage account breaks the persistence process and the import-export processes.
160155

161156
## Use managed identity to access a storage account
@@ -164,27 +159,27 @@ If you're not using managed identity and instead authorizing a storage account w
164159

165160
1. Open the Azure Cache for Redis instance that has been assigned the Storage Blob Data Contributor role and go to the **Data persistence** on the Resource menu.
166161

167-
2. Change the **Authentication Method** to **Managed Identity** and select the storage account you configured earlier in the article. select **Save**.
162+
1. Change the **Authentication Method** to **Managed Identity** and select the storage account you configured earlier in the article. select **Save**.
168163

169164
:::image type="content" source="media/cache-managed-identity/data-persistence.png" alt-text="Screenshot showing data persistence pane with authentication method selected.":::
170165

171166
> [!IMPORTANT]
172167
> The identity defaults to the system-assigned identity if it is enabled. Otherwise, the first listed user-assigned identity is used.
173168
>
174169
175-
3. Data persistence backups can now be saved to the storage account using managed identity authentication.
170+
1. Data persistence backups can now be saved to the storage account using managed identity authentication.
176171

177172
:::image type="content" source="media/cache-managed-identity/redis-persistence.png" alt-text="Screenshot showing export data in Resource menu.":::
178173

179174
### Use managed identity to import and export cache data
180175

181176
1. Open your Azure Cache for Redis instance that has been assigned the Storage Blob Data Contributor role and go to the **Import** or **Export** tab under **Administration**.
182177

183-
2. If importing data, choose the blob storage location that holds your chosen RDB file. If exporting data, type your desired blob name prefix and storage container. In both situations, you must use the storage account you've configured for managed identity access.
178+
1. If importing data, choose the blob storage location that holds your chosen RDB file. If exporting data, type your desired blob name prefix and storage container. In both situations, you must use the storage account you've configured for managed identity access.
184179

185180
:::image type="content" source="media/cache-managed-identity/export-data.png" alt-text="Screenshot showing Managed Identity selected.":::
186181

187-
3. Under **Authentication Method**, choose **Managed Identity** and select **Import** or **Export**, respectively.
182+
1. Under **Authentication Method**, choose **Managed Identity** and select **Import** or **Export**, respectively.
188183

189184
> [!NOTE]
190185
> It will take a few minutes to import or export the data.
@@ -193,7 +188,7 @@ If you're not using managed identity and instead authorizing a storage account w
193188
> [!IMPORTANT]
194189
>If you see an export or import failure, double check that your storage account has been configured with your cache's system-assigned or user-assigned identity. The identity used will default to system-assigned identity if it is enabled. Otherwise, the first listed user-assigned identity is used.
195190
196-
## Next steps
191+
## Related content
197192

198193
- [Learn more](cache-overview.md#service-tiers) about Azure Cache for Redis features
199194
- [What are managed identifies](../active-directory/managed-identities-azure-resources/overview.md)

0 commit comments

Comments
 (0)