Skip to content

Commit 1175c14

Browse files
authored
Merge branch 'MicrosoftDocs:main' into tds-for-sql
2 parents 976ee29 + bece2cd commit 1175c14

259 files changed

Lines changed: 3332 additions & 27332 deletions

File tree

Some content is hidden

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

.openpublishing.redirection.json

Lines changed: 215 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,215 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/azure-health-insights/configure-containers.md",
5+
"redirect_url": "/previous-versions/azure/azure-health-insights/configure-containers",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "articles/azure-health-insights/deploy-portal.md",
10+
"redirect_url": "/previous-versions/azure/azure-health-insights/deploy-portal",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "articles/azure-health-insights/get-started-cli.md",
15+
"redirect_url": "/previous-versions/azure/azure-health-insights/get-started-cli",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "articles/azure-health-insights/get-started-powershell.md",
20+
"redirect_url": "/previous-versions/azure/azure-health-insights/get-started-powershell",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "articles/azure-health-insights/index.yml",
25+
"redirect_url": "/previous-versions/azure/azure-health-insights/index",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "articles/azure-health-insights/overview.md",
30+
"redirect_url": "/previous-versions/azure/azure-health-insights/overview",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path": "articles/azure-health-insights/reliability-health-insights.md",
35+
"redirect_url": "/previous-versions/azure/azure-health-insights/reliability-health-insights",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path": "articles/azure-health-insights/use-containers.md",
40+
"redirect_url": "/previous-versions/azure/azure-health-insights/use-containers",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path": "articles/azure-health-insights/radiology-insights/age-mismatch-inference.md",
45+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/age-mismatch-inference",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path": "articles/azure-health-insights/radiology-insights/communication-inference.md",
50+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/communication-inference",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path": "articles/azure-health-insights/radiology-insights/complete-order-discrepancy-inference.md",
55+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/complete-order-discrepancy-inference",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path": "articles/azure-health-insights/radiology-insights/critical-result-inference.md",
60+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/critical-result-inference",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path": "articles/azure-health-insights/radiology-insights/faq.md",
65+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/faq",
66+
"redirect_document_id": false
67+
},
68+
{
69+
"source_path": "articles/azure-health-insights/radiology-insights/finding-inference.md",
70+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/finding-inference",
71+
"redirect_document_id": false
72+
},
73+
{
74+
"source_path": "articles/azure-health-insights/radiology-insights/get-started.md",
75+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/get-started",
76+
"redirect_document_id": false
77+
},
78+
{
79+
"source_path": "articles/azure-health-insights/radiology-insights/guidance-inference.md",
80+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/guidance-inference",
81+
"redirect_document_id": false
82+
},
83+
{
84+
"source_path": "articles/azure-health-insights/radiology-insights/index.yml",
85+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/index",
86+
"redirect_document_id": false
87+
},
88+
{
89+
"source_path": "articles/azure-health-insights/radiology-insights/inferences.md",
90+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/inferences",
91+
"redirect_document_id": false
92+
},
93+
{
94+
"source_path": "articles/azure-health-insights/radiology-insights/laterality-mismatch-inference.md",
95+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/laterality-mismatch-inference",
96+
"redirect_document_id": false
97+
},
98+
{
99+
"source_path": "articles/azure-health-insights/radiology-insights/limited-order-discrepancy-inference.md",
100+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/limited-order-discrepancy-inference",
101+
"redirect_document_id": false
102+
},
103+
{
104+
"source_path": "articles/azure-health-insights/radiology-insights/model-configuration.md",
105+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/model-configuration",
106+
"redirect_document_id": false
107+
},
108+
{
109+
"source_path": "articles/azure-health-insights/radiology-insights/overview.md",
110+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/overview",
111+
"redirect_document_id": false
112+
},
113+
{
114+
"source_path": "articles/azure-health-insights/radiology-insights/quality-measure-inference.md",
115+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/quality-measure-inference",
116+
"redirect_document_id": false
117+
},
118+
{
119+
"source_path": "articles/azure-health-insights/radiology-insights/radiology-procedure-inference.md",
120+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/radiology-procedure-inference",
121+
"redirect_document_id": false
122+
},
123+
{
124+
"source_path": "articles/azure-health-insights/radiology-insights/recommendation-inference.md",
125+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/recommendation-inference",
126+
"redirect_document_id": false
127+
},
128+
{
129+
"source_path": "articles/azure-health-insights/radiology-insights/scoring-and-assessment-inference.md",
130+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/scoring-and-assessment-inference",
131+
"redirect_document_id": false
132+
},
133+
{
134+
"source_path": "articles/azure-health-insights/radiology-insights/sex-mismatch-inference.md",
135+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/sex-mismatch-inference",
136+
"redirect_document_id": false
137+
},
138+
{
139+
"source_path": "articles/azure-health-insights/radiology-insights/support-and-help.md",
140+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/support-and-help",
141+
"redirect_document_id": false
142+
},
143+
{
144+
"source_path": "articles/azure-health-insights/radiology-insights/transparency-note.md",
145+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/transparency-note",
146+
"redirect_document_id": false
147+
},
148+
{
149+
"source_path": "articles/azure-health-insights/radiology-insights/tutorial.md",
150+
"redirect_url": "/previous-versions/azure/azure-health-insights/radiology-insights/tutorial",
151+
"redirect_document_id": false
152+
},
153+
{
154+
"source_path": "articles/azure-health-insights/responsible-ai/data-privacy-security.md",
155+
"redirect_url": "/previous-versions/azure/azure-health-insights/responsible-ai/data-privacy-security",
156+
"redirect_document_id": false
157+
},
158+
{
159+
"source_path": "articles/azure-health-insights/trial-matcher/faq.md",
160+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/faq",
161+
"redirect_document_id": false
162+
},
163+
{
164+
"source_path": "articles/azure-health-insights/trial-matcher/get-started.md",
165+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/get-started",
166+
"redirect_document_id": false
167+
},
168+
{
169+
"source_path": "articles/azure-health-insights/trial-matcher/index.yml",
170+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/index",
171+
"redirect_document_id": false
172+
},
173+
{
174+
"source_path": "articles/azure-health-insights/trial-matcher/inferences.md",
175+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/inferences",
176+
"redirect_document_id": false
177+
},
178+
{
179+
"source_path": "articles/azure-health-insights/trial-matcher/integration-and-responsible-use.md",
180+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/integration-and-responsible-use",
181+
"redirect_document_id": false
182+
},
183+
{
184+
"source_path": "articles/azure-health-insights/trial-matcher/model-configuration.md",
185+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/model-configuration",
186+
"redirect_document_id": false
187+
},
188+
{
189+
"source_path": "articles/azure-health-insights/trial-matcher/overview.md",
190+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/overview",
191+
"redirect_document_id": false
192+
},
193+
{
194+
"source_path": "articles/azure-health-insights/trial-matcher/patient-info.md",
195+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/patient-info",
196+
"redirect_document_id": false
197+
},
198+
{
199+
"source_path": "articles/azure-health-insights/trial-matcher/support-and-help.md",
200+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/support-and-help",
201+
"redirect_document_id": false
202+
},
203+
{
204+
"source_path": "articles/azure-health-insights/trial-matcher/transparency-note.md",
205+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/transparency-note",
206+
"redirect_document_id": false
207+
},
208+
{
209+
"source_path": "articles/azure-health-insights/trial-matcher/trial-matcher-modes.md",
210+
"redirect_url": "/previous-versions/azure/azure-health-insights/trial-matcher/trial-matcher-modes",
211+
"redirect_document_id": false
212+
},
3213
{
4214
"source_path": "articles/network-watcher/network-watcher-using-open-source-tools.md",
5215
"redirect_url": "/previous-versions/azure/network-watcher/network-watcher-using-open-source-tools",
@@ -6675,6 +6885,11 @@
66756885
"redirect_url": "/azure/reliability/reliability-nat-gateway",
66766886
"redirect_document_id": false
66776887
},
6888+
{
6889+
"source_path": "articles/synapse-analytics/sql/get-started-azure-data-studio.md",
6890+
"redirect_url": "/azure/synapse-analytics/sql/get-started-ssms",
6891+
"redirect_document_id": false
6892+
},
66786893
{
66796894
"source_path": "articles/cyclecloud/how-to/collect-custom-metrics-gpu-infiniband-telegraf.md",
66806895
"redirect_url": "/azure/cyclecloud/how-to/monitor-cyclecloud-cluster-using-prometheus-grafana",

articles/api-management/breaking-changes/trusted-service-connectivity-retirement-march-2026.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,12 @@ First, check for an Azure Advisor recommendation:
3737
1. If it does, update the networking configuration to eliminate the dependency on trusted service connectivity. If it doesn’t, proceed to the next step.
3838
1. Disable trusted service connectivity in your API Management gateway.
3939

40+
> [!NOTE]
41+
> Azure Advisor recommendation shows the Azure backend services your API Management instance has sent outbound requests to in the past 24 hours, regardless of the authentication method used.
42+
> Use this to identify the backends your API Management instance depends on and validate their configuration.
43+
>
44+
> If no traffic is reported, continue monitoring for a few days and disable the feature if results are consistent.
45+
4046
#### Scenarios that are not affected by the breaking change
4147

4248
All scenarios involving control plane operations that use trusted service connectivity remain supported and aren't affected by the breaking change, including accessing:

articles/app-service/deploy-intelligent-apps-dotnet-to-azure-sql.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: 'Deploy a .NET Blazor App Connected to Azure SQL and Azure OpenAI on Azur
33
description: Get started connecting Azure SQL to your OpenAI app
44
author: jeffwmartinez
55
ms.author: jefmarti
6-
ms.date: 04/17/2025
6+
ms.date: 02/04/2026
77
ms.update-cycle: 180-days
88
ms.topic: tutorial
99
ms.custom:
@@ -152,7 +152,7 @@ To perform a hybrid vector search on your Azure SQL database, you first need to
152152
153153
## 5. Create procedure to generate embeddings
154154

155-
With [Azure SQL vector support (preview)](https://devblogs.microsoft.com/azure-sql/announcing-eap-native-vector-support-in-azure-sql-database/), you can create a stored procedure that will use a Vector data type to store generated embeddings for search queries. The stored procedure invokes an external REST API endpoint to get the embeddings. See the [documentation](/azure-data-studio/quickstart-sql-database) to use Azure Data Studio to connect to your database before running the query.
155+
With [Azure SQL vector support (preview)](https://devblogs.microsoft.com/azure-sql/announcing-eap-native-vector-support-in-azure-sql-database/), you can create a stored procedure that will use a Vector data type to store generated embeddings for search queries. The stored procedure invokes an external REST API endpoint to get the embeddings. See the [MSSQL extension documentation](/sql/tools/visual-studio-code-extensions/mssql/mssql-extension-visual-studio-code) to use Visual Studio Code to connect to your database before running the query.
156156
157157
Use the following to create a stored procedure with your preferred SQL query editor. You need to populate the @url parameter with your Azure OpenAI resource name and populate the rest endpoint with the API key from your text embedding model. You'll notice the model name as part of the @url, which will be populated with your search query.
158158

articles/application-gateway/mutual-authentication-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Each SSL profile can support up to 100 trusted client CA certificate chains. A s
4949

5050
> [!NOTE]
5151
> * Mutual authentication is only available on Standard_v2 and WAF_v2 SKUs.
52-
> * Configuration of Mutual authentication for [TLS protocol listeners (preview)](tcp-tls-proxy-overview.md) is currently available through REST API, PowerShell, and CLI.
52+
> * Configuration of Mutual authentication for [TLS protocol listeners](tcp-tls-proxy-overview.md) is currently available through REST API, PowerShell, and CLI.
5353
5454
### Certificates supported for mutual TLS strict mode authentication
5555

0 commit comments

Comments
 (0)