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
| API threat detection with [Defender for APIs](protect-with-defender-for-apis.md)| ✔️ | ✔️ | ❌ | ❌ | ❌ |
90
90
91
91
<sup>1</sup> Depends on how the gateway is deployed, but is the responsibility of the customer.<br/>
92
92
<sup>2</sup> Connectivity to the self-hosted gateway v2 [configuration endpoint](self-hosted-gateway-overview.md#fqdn-dependencies) requires DNS resolution of the endpoint hostname.<br/>
93
93
<sup>3</sup> CA root certificates for self-hosted gateway are managed separately per gateway.<br/>
94
94
<sup>4</sup> Client protocol needs to be enabled.<br/>
95
95
<sup>5</sup> Configure using the [forward-request](forward-request-policy.md) policy.<br/>
96
-
<sup>6</sup> Configure CA certificate details for backend certificate authentication in [backend](backends.md) settings.
96
+
<sup>6</sup> Configure CA certificate details for backend certificate authentication in [backend](backends.md) settings.<br/>
97
+
<sup>7</sup> In preview for classic tier instances created starting January 2026. Contact support to enable for existing classic tier instances.
97
98
98
99
### Backend APIs
99
100
@@ -110,7 +111,7 @@ The following tables compare features available in the following API Management
<sup>1</sup> In preview for classic tier instances created starting January 2026. Contact support to enable for existing classic tier instances.
124
+
125
+
122
126
### Policies
123
127
124
128
Managed and self-hosted gateways support all available [policies](api-management-policies.md) in policy definitions with the following exceptions. See the policy reference for details about each policy.
Copy file name to clipboardExpand all lines: articles/data-factory/automatic-connector-upgrade.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.topic: concept-article
9
9
ms.custom:
10
10
- references_regions
11
11
- build-2025
12
-
ms.date: 03/24/2026
12
+
ms.date: 03/27/2026
13
13
---
14
14
15
15
# Automatic connector upgrade
@@ -72,8 +72,9 @@ You can find more details from the table below on the connector list that is pla
72
72
|[Google BigQuery](connector-google-bigquery.md)| Scenario that doesn't rely on below capability in Google BigQuery V1:<br><br> • Use `trustedCertsPath`, `additionalProjects`, `requestgoogledrivescope` connection properties.<br> • Set `useSystemTrustStore` connection property as `false`.<br> • Use **STRUCT** and **ARRAY** data types. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.58 or above. |
73
73
|[Greenplum](connector-greenplum.md)| If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.56 or above. |
74
74
|[Hive](connector-hive.md)| Scenario that doesn't rely on below capability in Hive (version 1.0):<br><br>• Use Username authentication type.<br>• Thrift transport protocol:<br> • HiveServer1<br>• Service discovery mode: True<br>• Use native query: True <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.59 or above.|
75
+
| [HubSpot](connector-hubspot.md) | The following HubSpot tables are supported for automatic upgrade:<br><br>Hubspot.Deal_Properties, Hubspot.Company_Properties, Hubspot.Deals, Hubspot.Deal_Associations_Associated_Vids, Hubspot.Contact_Properties, Hubspot.All_Deals, Hubspot.Contact_Lists, Hubspot.Deal_Properties_Options, Hubspot.Contact_Properties_Options, Hubspot.Companies_Properties_Values, Hubspot.Deal_Pipelines_Stages, Hubspot.Companies, Hubspot.Contacts, Hubspot.Deal_Properties_Values, Hubspot.Deal_Pipelines, CRM.Contact_Properties_Values, Hubspot.Deal_Associations_Associated_Company_Ids, Hubspot.Contacts_List_Memberships, Hubspot.Contacts_Identity_Profiles_Identities, Hubspot.TicketPipeLines, Hubspot.TicketPipeLinesStages, Hubspot.LineItemProperties, Hubspot.Deal_Property_Groups, Hubspot.CRMDealsPipeLinesStages, Hubspot.LineItemPropertiesOptions, Hubspot.Contact_Property_Groups, Hubspot.Contacts_Identity_Profiles, Hubspot.Users, Hubspot.EmailSubscriptions, Hubspot.CallEngagementDisposition, Hubspot.Tickets, Hubspot.Forms, CRM.CompanyProperties, CRM.DealProperties, CRM.Owners, CRM.LineItemProperties. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.64 or above. |
75
76
|[Impala](connector-impala.md)| Scenario that doesn't rely on below capability in Impala (version 1.0):<br><br>• Use SASL Username authentication type.<br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.59 or above. |
76
-
| [Jira](connector-jira.md) | Scenario that doesn't rely on below capability in Jira (version 1.0):<br><br>• Use `useEncryptedEndpoints`, `useHostVerification` and `usePeerVerification` as connection properties. <br>• Use `query`. <br><br>The following Jira tables are supported for automatic upgrade:<br> Platform.Api_Groups_Picker, Platform.Api_Issue_Type, Platform.Api_Project, Platform.Api_Field, Platform.Api_Status, Platform.Api_Status_Category, Platform.Api_Project_Type, Platform.Api_Resolution, Platform.Api_Priority, Platform.ApiAllUsers, Platform.Api_Issue_Link_Type, Platform.Api_Role, Platform.Api_Project_Versions, Platform.Api_Component, Platform.Api_Project_IssueTypes, Platform.Api_Issue, Agile.Agile_Board_Epic, Agile.Agile_Board, Agile.Agile_Board_Sprint, Agile.Column_Config_Columns, Agile.Agile_Board_Issue_Fields_Components, Agile.Agile_Board_Issue_Fields_Closed_Sprints, Agile.AgileBoardProjects. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.64 or above. |
77
+
| [Jira](connector-jira.md) | Scenario that doesn't rely on below capability in Jira (version 1.0):<br><br>• Use `useEncryptedEndpoints`, `useHostVerification` and `usePeerVerification` as connection properties. <br>• Use `query`. <br><br>The following Jira tables are supported for automatic upgrade:<br><br>Platform.Api_Groups_Picker, Platform.Api_Issue_Type, Platform.Api_Project, Platform.Api_Field, Platform.Api_Status, Platform.Api_Status_Category, Platform.Api_Project_Type, Platform.Api_Resolution, Platform.Api_Priority, Platform.ApiAllUsers, Platform.Api_Issue_Link_Type, Platform.Api_Role, Platform.Api_Project_Versions, Platform.Api_Component, Platform.Api_Project_IssueTypes, Platform.Api_Issue, Agile.Agile_Board_Epic, Agile.Agile_Board, Agile.Agile_Board_Sprint, Agile.Column_Config_Columns, Agile.Agile_Board_Issue_Fields_Components, Agile.Agile_Board_Issue_Fields_Closed_Sprints, Agile.AgileBoardProjects. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.64 or above. |
77
78
|[MariaDB](connector-mariadb.md)| If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.58 or above. |
78
79
|[MySQL](connector-mysql.md)| If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.58 or above. |
79
80
|[Netezza](connector-netezza.md)| If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.59 or above. |
@@ -87,7 +88,7 @@ You can find more details from the table below on the connector list that is pla
87
88
|[Spark](connector-spark.md)| Scenario that doesn't rely on below capability in Spark (version 1.0):<br><br>• Use Username authentication type. <br>• Thrift transport protocol:<br> • SASL<br> • Binary<br>• Thrift transport protocol:<br> • SharkServer<br> • SharkServer2<br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.59 or above.|
88
89
|[Teradata](connector-teradata.md)| Scenario that doesn't rely on below capability in Teradata (version 1.0):<br><br> • Set below value for **CharacterSet**:<br> • BIG5 (TCHBIG5_1R0)<br> • EUC (Unix compatible, KANJIEC_0U)<br> • GB (SCHGB2312_1T0)<br> • IBM Mainframe (KANJIEBCDIC5035_0I)<br> • NetworkKorean (HANGULKSC5601_2R4)<br> • Shift-JIS (Windows, DOS compatible, KANJISJIS_0S)<br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.58 or above.|
89
90
|[Vertica](connector-vertica.md)| Scenario that doesn't rely on below capability in Vertica (version 1.0):<br><br>• Linked service that uses Azure integration runtime.<br><br>Automatic upgrade is only applicable when the driver is installed in your machine that installs the self-hosted integration runtime (version 5.56 or above).<br><br> For more information, go to [Install Vertica ODBC driver for the version 2.0](connector-vertica.md#install-vertica-odbc-driver-for-the-version-20). |
90
-
| [Xero](connector-xero.md) | Scenario that doesn't rely on below capability in Xero (version 1.0):<br><br>• Use OAuth 1.0 authentication type. <br><br>The following Xero tables are supported for automatic upgrade: <br> Accounts, AssetSettings, AssetTypes, Associations, Bank_Transaction_Line_Item_Tracking, Bank_Transaction_Line_Items, Bank_Transactions, Bank_Transfers, BankFeedConnections, Branding_Themes, Budgets, Contact_Group_Contacts, Contact_Groups, Contacts, Contacts_Addresses, Contacts_Contact_Persons, Contacts_Phones, Contacts_Purchases_Tracking_Categories, Contacts_Sales_Tracking_Categories, Credit_Note_Line_Items, Credit_Notes, Credit_Notes_Allocations, Credit_Notes_Line_Items_Tracking, Currencies, Employees, Expense_Claim_Payments, Expense_Claim_Receipts, Expense_Claim_Validation_Errors, Expense_Claims, Files, Folders, Invoice_Line_Items, Invoices, Invoices_Credit_Notes, Invoices_Line_Items_Tracking, Invoices_Overpayments, Invoices_Prepayments, Items, Journal_Line_Tracking_Categories, Journal_Line_Tracking_Categories_Options, Journal_Lines, Journals, Manual_Journal_Line_Tracking, Manual_Journal_Lines, Manual_Journals, Organisation_Addresses, Organisation_External_Links, Organisation_Phones, Organisations, Overpayment_Line_Items, Overpayment_Line_Items_Tracking, Overpayments, Overpayments_Allocations, Payments, Prepayment_Line_Item_Tracking, Prepayment_Line_Items, Prepayments, Prepayments_Allocations, ProjectTasks, ProjectUsers, Projects, Purchase_Order_Line_Item_Tracking, Purchase_Order_Line_Items, Purchase_Orders, Quotes, Receipt_Line_Item_Tracking, Receipt_Line_Items, Receipt_Validation_Errors, Receipts, Repeating_Invoice_Line_Item_Tracking, Repeating_Invoice_Line_Items, Repeating_Invoices, Statements, Tax_Rate_Tax_Components, Tax_Rates, Time, Tracking_Categories, Tracking_Category_Options, Users. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.62 or above. |
91
+
| [Xero](connector-xero.md) | Scenario that doesn't rely on below capability in Xero (version 1.0):<br><br>• Use OAuth 1.0 authentication type. <br><br>The following Xero tables are supported for automatic upgrade: <br><br>Accounts, AssetSettings, AssetTypes, Associations, Bank_Transaction_Line_Item_Tracking, Bank_Transaction_Line_Items, Bank_Transactions, Bank_Transfers, BankFeedConnections, Branding_Themes, Budgets, Contact_Group_Contacts, Contact_Groups, Contacts, Contacts_Addresses, Contacts_Contact_Persons, Contacts_Phones, Contacts_Purchases_Tracking_Categories, Contacts_Sales_Tracking_Categories, Credit_Note_Line_Items, Credit_Notes, Credit_Notes_Allocations, Credit_Notes_Line_Items_Tracking, Currencies, Employees, Expense_Claim_Payments, Expense_Claim_Receipts, Expense_Claim_Validation_Errors, Expense_Claims, Files, Folders, Invoice_Line_Items, Invoices, Invoices_Credit_Notes, Invoices_Line_Items_Tracking, Invoices_Overpayments, Invoices_Prepayments, Items, Journal_Line_Tracking_Categories, Journal_Line_Tracking_Categories_Options, Journal_Lines, Journals, Manual_Journal_Line_Tracking, Manual_Journal_Lines, Manual_Journals, Organisation_Addresses, Organisation_External_Links, Organisation_Phones, Organisations, Overpayment_Line_Items, Overpayment_Line_Items_Tracking, Overpayments, Overpayments_Allocations, Payments, Prepayment_Line_Item_Tracking, Prepayment_Line_Items, Prepayments, Prepayments_Allocations, ProjectTasks, ProjectUsers, Projects, Purchase_Order_Line_Item_Tracking, Purchase_Order_Line_Items, Purchase_Orders, Quotes, Receipt_Line_Item_Tracking, Receipt_Line_Items, Receipt_Validation_Errors, Receipts, Repeating_Invoice_Line_Item_Tracking, Repeating_Invoice_Line_Items, Repeating_Invoices, Statements, Tax_Rate_Tax_Components, Tax_Rates, Time, Tracking_Categories, Tracking_Category_Options, Users. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.62 or above. |
Copy file name to clipboardExpand all lines: articles/iot-operations/discover-manage-assets/howto-use-management-actions.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ The `az iot ops mgmt-actions enable` command in the quickstart script provisions
41
41
| Event Grid data flow endpoint | Connects the Azure IoT Operations data flow runtime to the Event Grid namespace. |
42
42
| Request data flow graph | Routes messages from Event Grid to the MQTT broker, applying a WASM module to rewrite topic paths. |
43
43
| Response data flow | Routes responses from the MQTT broker back to Event Grid. |
44
-
| Managed identity | If you don't specify a user-assigned managed identity, the command creates a system-assigned managed identity for the data flow endpoint and Azure Device Registry namespace. If the Azure Device Registry namespace doesn't have a system-assigned managed identity enabled, the `az iot ops mgmt-actions enable` command enables one to allow authentication with the Event Grid namespace. |
44
+
| Managed identity | If you don't specify a user-assigned managed identity, the command creates a system-assigned managed identity for the data flow endpoint. If the Azure Device Registry namespace doesn't have a system-assigned managed identity enabled, the `az iot ops mgmt-actions enable` command enables one to allow authentication with the Event Grid namespace. |
45
45
| Role assignments | Grants the data flow identity and the Azure Device Registry namespace the required permissions. |
46
46
| Management endpoint | A management endpoint for the Azure Device Registry namespace linking it to the Event Grid namespace. |
Copy file name to clipboardExpand all lines: articles/network-watcher/connection-troubleshoot-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Connection troubleshoot reduces the Mean Time To Resolution (MTTR) by providing
25
25
- Graphical topology view from source to destination
26
26
- Number of probes failed during the connection troubleshoot check
27
27
28
-
## Agentless experience (preview)
28
+
## Agentless experience
29
29
30
30
Connection troubleshoot now supports an agentless experience (currently in preview). You no longer need to install the Network Watcher agent VM extension on your virtual machines to run connectivity tests. Features and functionality may change before general availability.
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments