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
This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from Jira. It builds on the [copy activity overview](copy-activity-overview.md) article that presents a general overview of copy activity.
19
19
20
+
> [!IMPORTANT]
21
+
> The Jira connector version 2.0 provides improved native Jira support. If you are using Jira connector version 1.0 in your solution, please [upgrade the Jira connector](#upgrade-the-jira-connector-from-version-10-to-version-20) before **March 31, 2026**. Refer to this [section](#jira-connector-lifecycle-and-upgrade) for details on the difference between version 2.0 and version 1.0.
22
+
20
23
## Supported capabilities
21
24
22
25
This Jira connector is supported for the following capabilities:
@@ -65,7 +68,50 @@ The following sections provide details about properties that are used to define
65
68
66
69
## Linked service properties
67
70
68
-
The following properties are supported for Jira linked service:
71
+
The Jira connector now supports version 2.0. Refer to this [section](#jira-connector-lifecycle-and-upgrade) to upgrade your Jira connector version from version 1.0. For the property details, see the corresponding sections.
72
+
73
+
-[Version 2.0](#version-20)
74
+
-[Version 1.0](#version-10)
75
+
76
+
### Version 2.0
77
+
78
+
The Jira linked service supports the following properties when applying version 2.0:
79
+
80
+
| Property | Description | Required |
81
+
|:--- |:--- |:--- |
82
+
| type | The type property must be set to: **Jira**| Yes |
83
+
| version | The version that you specify. The value is `2.0`. | Yes |
84
+
| host | The IP address or host name of the Jira service. For example, `jira.example.com`. | Yes |
85
+
| port | The TCP port that the Jira server uses to listen for client connections. The default value is 443 if connecting through HTTPS, or 8080 if connecting through HTTP. | No |
86
+
| username | The user name that you use to access Jira Service. | Yes |
87
+
| password | The [Atlassian API token](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/) (if two-step verification is enabled on the Atlassian account) or password corresponding to the user name that you provided in the username field. Mark this field as a SecureString to store it securely, or [reference a secret stored in Azure Key Vault](store-credentials-in-key-vault.md). | Yes |
88
+
| connectVia | The [integration runtime](concepts-integration-runtime.md) to be used to connect to the data store. If no value is specified, the property uses the default Azure integration runtime. You can use the self-hosted integration runtime and its version should be 5.61 or above. | No |
89
+
90
+
91
+
**Example:**
92
+
93
+
```json
94
+
{
95
+
"name": "JiraLinkedService",
96
+
"properties": {
97
+
"type": "Jira",
98
+
"version": "2.0",
99
+
"typeProperties": {
100
+
"host" : "<host>",
101
+
"port" : "<port>",
102
+
"username" : "<username>",
103
+
"password": {
104
+
"type": "SecureString",
105
+
"value": "<password>"
106
+
}
107
+
}
108
+
}
109
+
}
110
+
```
111
+
112
+
### Version 1.0
113
+
114
+
The Jira linked service supports the following properties when applying version 1.0:
69
115
70
116
| Property | Description | Required |
71
117
|:--- |:--- |:--- |
@@ -107,7 +153,9 @@ To copy data from Jira, set the type property of the dataset to **JiraObject**.
107
153
| Property | Description | Required |
108
154
|:--- |:--- |:--- |
109
155
| type | The type property of the dataset must be set to: **JiraObject**| Yes |
110
-
| tableName | Name of the table. | No (if "query" in activity source is specified) |
156
+
| schema | Name of the schema. This property is only supported in version 2.0. | Yes |
157
+
| table | Name of the table. This property is only supported in version 2.0. | Yes |
158
+
| tableName | Name of the table. This property is only supported in version 1.0.| No (if "query" in activity source is specified) |
111
159
112
160
**Example**
113
161
@@ -126,11 +174,89 @@ To copy data from Jira, set the type property of the dataset to **JiraObject**.
126
174
}
127
175
```
128
176
177
+
The connector version 2.0 supports the following Jira tables:
178
+
179
+
- AdvancedSettings
180
+
- AllAccessibleProjectTypes
181
+
- AllApplicationRoles
182
+
- AllAvailableDashboardGadgets
183
+
- AllDashboards
184
+
- AllFieldConfigurations
185
+
- AllFieldConfigurationSchemes
186
+
- AllIssueTypeSchemes
187
+
- AllLabels
188
+
- AllPermissions
189
+
- AllPermissionSchemes
190
+
- AllProjectCategories
191
+
- AllProjectRoles
192
+
- AllProjectTypes
193
+
- AllUserDataClassificationLevels
194
+
- AllUsers
195
+
- AllUsersDefault
196
+
- AllWorkflowSchemes
197
+
- ApplicationProperty
198
+
- ApproximateLicenseCount
199
+
- AttachmentMeta
200
+
- AutoComplete
201
+
- AvailableTimeTrackingImplementations
202
+
- Banner
203
+
- BulkGetGroups
204
+
- Configuration
205
+
- CurrentUser
206
+
- DashboardsPaginated
207
+
- DefaultEditor
208
+
- DefaultShareScope
209
+
- Events
210
+
- FavouriteFilters
211
+
- FieldAutoCompleteForQueryString
212
+
- FieldConfigurationSchemeMappings
213
+
- Fields
214
+
- FieldsPaginated
215
+
- FiltersPaginated
216
+
- FindComponentsForProjects
217
+
- FindGroups
218
+
- IdsOfWorklogsDeletedSince
219
+
- IdsOfWorklogsModifiedSince
220
+
- IssueAllTypes
221
+
- IssueLimitReport
222
+
- IssueLinkTypes
223
+
- IssueNavigatorDefaultColumns
224
+
- IssuePickerResource
225
+
- IssueSecuritySchemes
226
+
- IssueTypeSchemesMapping
227
+
- IssueTypeScreenSchemeMappings
228
+
- IssueTypeScreenSchemes
229
+
- License
230
+
- Locale
231
+
- MyFilters
232
+
- NotificationSchemes
233
+
- NotificationSchemeToProjectMappings
234
+
- Plans
235
+
- PrioritySchemes
236
+
- Recent
237
+
- Screens
238
+
- ScreenSchemes
239
+
- Search
240
+
- SearchProjects
241
+
- SearchProjectsUsingSecuritySchemes
242
+
- SearchResolutions
243
+
- SearchSecuritySchemes
244
+
- SearchWorkflows
245
+
- SecurityLevelMembers
246
+
- SecurityLevels
247
+
- SelectedTimeTrackingImplementation
248
+
- ServerInfo
249
+
- SharedTimeTrackingConfiguration
250
+
- StatusCategories
251
+
- Statuses
252
+
- TrashedFieldsPaginated
253
+
- UserDefaultColumns
254
+
129
255
## Copy activity properties
130
256
131
257
For a full list of sections and properties available for defining activities, see the [Pipelines](concepts-pipelines-activities.md) article. This section provides a list of properties supported by Jira source.
132
258
133
-
### JiraSource as source
259
+
### Jira as source
134
260
135
261
To copy data from Jira, set the source type in the copy activity to **JiraSource**. The following properties are supported in the copy activity **source** section:
136
262
@@ -139,6 +265,9 @@ To copy data from Jira, set the source type in the copy activity to **JiraSource
139
265
| type | The type property of the copy activity source must be set to: **JiraSource**| Yes |
140
266
| query | Use the custom SQL query to read data. For example: `"SELECT * FROM MyTable"`. | No (if "tableName" in dataset is specified) |
141
267
268
+
> [!NOTE]
269
+
> `query` is not supported in version 2.0.
270
+
142
271
**Example:**
143
272
144
273
```json
@@ -171,9 +300,44 @@ To copy data from Jira, set the source type in the copy activity to **JiraSource
171
300
]
172
301
```
173
302
303
+
## Data type mapping for Jira
304
+
305
+
When you copy data from Jira, the following mappings apply from Jira's data types to the internal data types used by the service. To learn about how the copy activity maps the source schema and data type to the sink, see [Schema and data type mappings](copy-activity-schema-and-type-mapping.md).
306
+
307
+
| Jira data type | Interim service data type (for version 2.0) | Interim service data type (for version 1.0) |
To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
177
319
320
+
## Jira connector lifecycle and upgrade
321
+
322
+
The following table shows the release stage and change logs for different versions of the Jira connector:
323
+
324
+
| Version | Release stage | Change log |
325
+
| :----------- | :------- |:------- |
326
+
| Version 1.0 | End of support announced | / |
327
+
| Version 2.0 | GA version available | • Support `schema` and `table` in Dataset. <br><br>• Support specific Jira tables. For the supported table list, go to [Dataset properties](#dataset-properties). <br><br>• The self-hosted integration runtime version should be 5.61 or above. <br><br>• The data type mapping for the Jira linked service version 2.0 is different from that for the version 1.0. For the latest data type mapping, go to [Data type mapping for Jira](#data-type-mapping-for-jira). <br><br>• `useEncryptedEndpoints`, `useHostVerification`, `usePeerVerification` are not supported in the linked service. <br><br> • `query` is not supported. <br><br> • OAuth 1.0 authentication is not supported. |
328
+
329
+
### Upgrade the Jira connector from version 1.0 to version 2.0
330
+
331
+
1. In **Edit linked service** page, select version 2.0 and configure the linked service by referring to [Linked service properties version 2.0](#version-20).
332
+
333
+
1. The data type mapping for the Jira linked service version 2.0 is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Jira](#data-type-mapping-for-jira).
334
+
335
+
1. If you use the self-hosted integration runtime, its version should be 5.61 or above.
336
+
337
+
1.`query` is only supported in version 1.0. You should use `schema` and `table` instead of `query` in version 2.0.
338
+
339
+
> [!NOTE]
340
+
> Version 2.0 supports specific Jira tables. For the supported table list, go to [Dataset properties](#dataset-properties).
341
+
178
342
## Related content
179
343
For a list of data stores supported as sources and sinks by the copy activity, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).
Copy file name to clipboardExpand all lines: articles/iot-operations/configure-observability-monitoring/howto-configure-observability.md
+19-25Lines changed: 19 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to deploy Azure IoT Operations observability resources, c
4
4
author: sethmanheim
5
5
ms.author: sethm
6
6
ms.topic: how-to
7
-
ms.date: 11/20/2025
7
+
ms.date: 12/19/2025
8
8
9
9
# CustomerIntent: As an IT admin or operator, I want to be able to monitor and visualize data on the health of my industrial assets and edge environment.
10
10
---
@@ -98,61 +98,55 @@ Define and deploy an [OpenTelemetry (OTel) Collector](https://opentelemetry.io/d
98
98
image:
99
99
repository: otel/opentelemetry-collector
100
100
tag: 0.107.0
101
+
101
102
config:
102
103
processors:
103
104
memory_limiter:
104
105
limit_percentage: 80
105
106
spike_limit_percentage: 10
106
-
check_interval: '60s'
107
+
check_interval: 60s
108
+
107
109
receivers:
108
-
jaeger: null
109
-
prometheus: null
110
-
zipkin: null
111
110
otlp:
112
111
protocols:
113
112
grpc:
114
-
endpoint: ':4317'
113
+
endpoint: ":4317"
115
114
http:
116
-
endpoint: ':4318'
115
+
endpoint: ":4318"
116
+
117
117
exporters:
118
118
prometheus:
119
-
endpoint: ':8889'
119
+
endpoint: ":8889"
120
120
resource_to_telemetry_conversion:
121
121
enabled: true
122
122
add_metric_suffixes: false
123
+
123
124
service:
124
125
extensions:
125
126
- health_check
127
+
128
+
telemetry:
129
+
metrics:
130
+
readers: []
131
+
126
132
pipelines:
127
133
metrics:
128
134
receivers:
129
135
- otlp
130
136
exporters:
131
137
- prometheus
132
-
logs: null
133
-
traces: null
134
-
telemetry: null
135
-
extensions:
136
-
memory_ballast:
137
-
size_mib: 0
138
+
138
139
resources:
139
140
limits:
140
-
cpu: '100m'
141
-
memory: '512Mi'
141
+
cpu: "100m"
142
+
memory: "512Mi"
143
+
142
144
ports:
143
145
metrics:
144
146
enabled: true
145
147
containerPort: 8889
146
148
servicePort: 8889
147
-
protocol: 'TCP'
148
-
jaeger-compact:
149
-
enabled: false
150
-
jaeger-grpc:
151
-
enabled: false
152
-
jaeger-thrift:
153
-
enabled: false
154
-
zipkin:
155
-
enabled: false
149
+
protocol: TCP
156
150
```
157
151
158
152
1. In the `otel-collector-values.yaml` file, make a note of the following values that you use in the `az iot ops create` command when you deploy Azure IoT Operations on the cluster:
* The *minimum validated version* is the lowest version of the Kubernetes distribution that Microsoft uses to validate Azure IoT Operations deployments.
Copy file name to clipboardExpand all lines: articles/networking/load-balancer-content-delivery/load-balancing-content-delivery-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
@@ -57,7 +57,7 @@ Azure offers several load-balancing and content delivery services, each caterin
57
57
-**High availability**: Enhances the availability of your applications by distributing traffic within and across zones.
58
58
-**Internal or public load balancing**: Supports both internal (within a virtual network) and public (internet-facing) load balancing scenarios.
59
59
-**Low latency and high throughput**: Ideal for applications requiring low latency and high throughput, such as gaming or real-time communication apps.
60
-
-
60
+
61
61
> [!NOTE]
62
62
> Clustering technologies, such as Azure Container Apps or Azure Kubernetes Service, contain load balancing constructs that operate mostly within the scope of their own cluster boundary, routing traffic to available application instances based on readiness and health probes. Those load balancing options aren't covered in this article.
Copy file name to clipboardExpand all lines: articles/partner-solutions/datadog/manage.md
+13-5Lines changed: 13 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,12 +69,16 @@ The column **Logs to Datadog** indicates whether the resource is sending logs to
69
69
70
70
When you add or remove subscriptions for Datadog monitoring, the system updates the Monitoring Reader role assignment on the System Managed Identity linked to the resource.
71
71
72
-
**Prerequisites**
72
+
### Prerequisites
73
73
74
-
To perform these actions, you must have both of the following Azure permissions:
74
+
-To perform these actions, you must have both of the following Azure permissions:
75
75
76
-
-`Microsoft.Authorization/roleAssignments/write`
77
-
-`Microsoft.Authorization/roleAssignments/delete`
76
+
-`Microsoft.Authorization/roleAssignments/write`
77
+
-`Microsoft.Authorization/roleAssignments/delete`
78
+
79
+
- The resource provider for Datadog (Microosoft.Datadog) must be registered in the target subscription.
80
+
81
+
### Add subscriptions
78
82
79
83
To monitor multiple subscriptions:
80
84
@@ -89,7 +93,8 @@ To monitor multiple subscriptions:
89
93
1. Select the subscriptions you want to monitor through the Datadog resource and select **Add**.
90
94
91
95
> [!IMPORTANT]
92
-
> Setting separate tag rules for different subscriptions isn't supported.
96
+
> - When you link a subscription to a Datadog resource, ensure that the subscription isn't scope locked (read-only or delete locks). Scope locks can prevent the addition and removal of diagnostic settings. For more information, see [Lock your Azure resources](../../azure-resource-manager/management/lock-resources.md).
97
+
> - Setting separate tag rules for different subscriptions isn't supported.
93
98
94
99
Diagnostics settings are automatically added to the subscription's resources that match the defined tag rules.
95
100
@@ -99,6 +104,9 @@ Once the subscription is added, the status changes to *Active*.
99
104
100
105
### Remove subscriptions
101
106
107
+
> [!IMPORTANT]
108
+
> When you unlink a subscription from a Datadog resource, ensure that the subscription isn't scope locked (read-only or delete locks). Scope locks can prevent the addition and removal of diagnostic settings. For more information, see [Lock your Azure resources](../../azure-resource-manager/management/lock-resources.md).
109
+
102
110
To unlink subscriptions from a Datadog resource:
103
111
104
112
1. Select **Datadog organization configurations > Monitored Subscriptions** from the service menu.
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments