Skip to content

Commit 51e65a6

Browse files
authored
Merge branch 'MicrosoftDocs:main' into main
2 parents a85c964 + a72de4d commit 51e65a6

File tree

2 files changed

+5
-2
lines changed

2 files changed

+5
-2
lines changed

articles/devtest-labs/image-factory-create.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ An image factory is a configuration-as-code solution that builds and distributes
1616

1717
The significant accelerator to get a developer desktop to a ready state in DevTest Labs is using custom images. The downside of custom images is that there's something extra to maintain in the lab. For example, trial versions of products expire over time (or) newly released security updates aren't applied, which force us to refresh the custom image periodically. With an image factory, you have a definition of the image checked in to source code control and have an automated process to produce custom images based on the definition.
1818

19-
The solution enables the speed of creating virtual machines from custom images while eliminating extra ongoing maintenance costs. With this solution, you can automatically create custom images, distribute them to other DevTest Labs, and retire the old images. In the following video, you learn about the image factory, and how it's implemented with DevTest Labs. All the Azure PowerShell scripts are freely available and located here: [https://aka.ms/dtlimagefactory](https://aka.ms/dtlimagefactory).
19+
The solution enables the speed of creating virtual machines from custom images while eliminating extra ongoing maintenance costs. With this solution, you can automatically create custom images, distribute them to other DevTest Labs, and retire the old images. All the Azure PowerShell scripts are freely available and located here: [https://aka.ms/dtlimagefactory](https://aka.ms/dtlimagefactory).
2020

2121
<br/>
2222

articles/search/search-indexer-howto-access-private.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: cognitive-search
1010
ms.custom:
1111
- ignite-2023
1212
ms.topic: how-to
13-
ms.date: 07/24/2023
13+
ms.date: 01/16/2024
1414
---
1515

1616
# Make outbound connections through a shared private link
@@ -88,6 +88,7 @@ You can create a shared private link for the following resources.
8888
| Microsoft.DBforMySQL/servers (preview) | `mysqlServer`|
8989
| Microsoft.Web/sites (preview) <sup>3</sup> | `sites` |
9090
| Microsoft.Sql/managedInstances (preview) <sup>4</sup>| `managedInstance` |
91+
| Microsoft.CognitiveServices/accounts (preview) <sup>5</sup>| `openai_account` |
9192

9293
<sup>1</sup> If Azure Storage and Azure AI Search are in the same region, the connection to storage is made over the Microsoft backbone network, which means a shared private link is redundant for this configuration. However, if you already set up a private endpoint for Azure Storage, you should also set up a shared private link or the connection is refused on the storage side. Also, if you're using multiple storage formats for various scenarios in search, make sure to create a separate shared private link for each sub-resource.
9394

@@ -97,6 +98,8 @@ You can create a shared private link for the following resources.
9798

9899
<sup>4</sup> See [Create a shared private link for a SQL Managed Instance](search-indexer-how-to-access-private-sql.md) for instructions.
99100

101+
<sup>5</sup> The `Microsoft.CognitiveServices/accounts` resource type is used for indexer connections to Azure OpenAI when implementing [integrated Vectorization](vector-search-integrated-vectorization.md).
102+
100103
## 1 - Create a shared private link
101104

102105
Use the Azure portal, Management REST API, the Azure CLI, or Azure PowerShell to create a shared private link.

0 commit comments

Comments
 (0)