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
Copy file name to clipboardExpand all lines: articles/search/search-indexer-how-to-access-private-sql.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ For more information about connection properties, see [Create an Azure SQL Manag
99
99
100
100
Provide the same shared private link name that you specified in the JSON body.
101
101
102
-
Provide a path to the create-pe.json file if you've navigated away from the file location. You can type `dir` at the command line to confirm the file is in the current directory.
102
+
Provide a path to the *create-pe.json* file if you've navigated away from the file location. You can type `dir` at the command line to confirm the file is in the current directory.
103
103
104
104
1. Press Enter to run the command.
105
105
@@ -180,22 +180,23 @@ This article assumes Postman or equivalent tool, and uses the REST APIs to make
180
180
181
181
1. Run the indexer. If the indexer execution succeeds and the search index is populated, the shared private link is working.
182
182
183
-
After the indexer is created successfully, it should connect over the private endpoint connection. You can monitor the status of the indexer by using the [Indexer Status API](/rest/api/searchservice/get-indexer-status).
183
+
You can monitor the status of the indexer in Azure portal or by using the [Indexer Status API](/rest/api/searchservice/get-indexer-status).
184
184
185
185
## 8 - Test the shared private link
186
186
187
187
If you ran the indexer in the previous step and successfully indexed content from your managed instance, then the test was successful. You can use [**Search explorer**](search-explorer.md) in Azure portal to check the contents of the index.
188
188
189
-
However, if the test failed or there's no content, you can modify your objects and repeat testing by choosing any client that can invoke an outbound request from an indexer. An easy choice is [running an indexer](search-howto-run-reset-indexers.md) in Azure portal, but you can also try the Postman and REST APIs for more precision.
189
+
However, if the indexer fails or there's no content in the index, you can modify your objects and repeat testing by choosing any client that can invoke an outbound request from an indexer. An easy choice is [running an indexer](search-howto-run-reset-indexers.md) in Azure portal, but you can also try Postman and REST APIs for more precision.
190
190
191
191
Assuming that your search service isn't also configured for a private connection, the REST client connection to Search can be over the public internet.
192
192
193
193
Here are some reminders for testing:
194
194
195
-
+ If you use Postman or another web testing tool, make sure the API version is a [preview Management REST API version](/rest/api/searchmanagement/management-api-versions) to create the shared private link. You can use a [stable Search REST API version](/rest/api/searchservice/search-service-api-versions) to create and invoke indexers and data sources.
196
-
+ You can use the Import data wizard, but initially the generated indexer won't have the correct execution environment setting.
195
+
+ If you use Postman or another web testing tool, use the [Management REST API](/rest/api/searchmanagement/) and a [preview API version](/rest/api/searchmanagement/management-api-versions) to create the shared private link. Use the [Search REST API](/rest/api/searchservice/) and a [stable API version](/rest/api/searchservice/search-service-api-versions) to create and invoke indexers and data sources.
196
+
+ You can use the Import data wizard to create an indexer, data source, and index. However, the generated indexer won't have the correct execution environment setting.
197
197
+ You can edit data source and indexer JSON in Azure portal to change properties, including the execution environment and the connection string.
198
198
+ You can reset and rerun the indexer in Azure portal. Reset is important for this scenario because it forces a full reprocessing of all documents.
199
+
+ You can use Search explorer to check the contents of the index.
0 commit comments