Microsoft Azure を Jira 自動化で使用する

はじめる前に

To manage Jira automations, you must have the appropriate space permissions:

• Company-managed spaces: You’ll need the Administer space and Browse space permissions for your space. Learn more about permissions for company-managed spaces

• Team-managed spaces: You’ll need Administrator app access for your space. Learn more about permissions for team-managed spaces

To manage global automations, you’ll need the Administer Jira permission. Learn more about global permissions in Jira Cloud.

Integrate your automation with Microsoft Azure

1. Automation に移動して [ルールを作成] を選択します。

2. Select a Microsoft Azure action for your automation. You can find a list of available actions later in this article.

3. [接続] を選択して、Microsoft Azure との接続を作成します。接続すると、自動化ルールによって他のツールや製品で変更を加えられるようになります。

4. Microsoft アカウントにサインインして [許可] を選択すると、Atlassian Automation から Microsoft Azure の情報にアクセスするという、リクエストされていた権限が付与されます。

Use Microsoft Azure actions in your automation

Cosmos DB Spoke actions

List Azure Cassandra keyspaces

You can use this action to list Cassandra keyspaces in an Azure Cosmos DB account. Use it to discover existing keyspaces before running operations on them. Enter the following fields or select using smart values:

• Subscription ID
  Enter the Azure subscription ID that contains the Cosmos DB account. This identifies where the account is hosted.

• Resource group name
  Enter the Azure resource group name that contains the Cosmos DB account. This narrows the search to a specific group.

• Account name
  Enter the Azure Cosmos DB account name. This is the account whose Cassandra keyspaces you want to list.

If the action fails, check that the subscription ID, resource group name, and account name exactly match the values shown in the Azure portal.

Get Azure keyspace throughput

You can use this action to get throughput settings for a Cassandra keyspace in Azure Cosmos DB. Use it to review or audit provisioned throughput before making changes. Enter the following fields or select using smart values:

• Subscription ID
  Enter the Azure subscription ID that contains the Cosmos DB account. This identifies where the keyspace is hosted.

• Resource group name
  Enter the Azure resource group name that contains the Cosmos DB account. This narrows the search to a specific group.

• Account name
  Enter the Azure Cosmos DB account name. This is the account that holds the Cassandra keyspace.

• Keyspace name
  Enter the Cassandra keyspace name to get throughput for. Use the exact keyspace name from Azure Cosmos DB.

If the action fails, confirm that the subscription ID, resource group name, account name, and keyspace name are valid and match the values in Azure Cosmos DB.

List Azure Cassandra tables

You can use this action to list Cassandra tables in an Azure Cosmos DB keyspace. Use it to explore tables before you read or update data. Enter the following fields or select using smart values:

• Subscription ID
  Enter the Azure subscription ID that contains the Cosmos DB account. This identifies where the keyspace is hosted.

• Resource group name
  Enter the Azure resource group name that contains the Cosmos DB account. This narrows the search to a specific group.

• Account name
  Enter the Azure Cosmos DB account name. This is the account that holds the Cassandra keyspace.

• Keyspace name
  Enter the Cassandra keyspace name to list tables from. Use the exact keyspace name from Azure Cosmos DB.

You’ll see a list of Cassandra tables in the specified keyspace. If no tables are returned, check that the keyspace name is correct and exists in the target account.

Get Azure Cassandra table

You can use this action to get properties of a Cassandra table in Azure Cosmos DB. Use it to review configuration details before changing throughput or schema. Enter the following fields or select using smart values:

• Subscription ID
  Enter the Azure subscription ID that contains the Cosmos DB account. This identifies where the table is hosted.

• Resource group name
  Enter the Azure resource group name that contains the Cosmos DB account. This narrows the search to a specific group.

• Account name
  Enter the Azure Cosmos DB account name. This is the account that holds the Cassandra keyspace and table.

• Keyspace name
  Enter the Cassandra keyspace name that contains the table. Use the exact keyspace name from Azure Cosmos DB.

• Table name
  Enter the Cassandra table name to retrieve. Use the exact table name as it appears in the keyspace.

If the action fails, confirm that the subscription, resource group, account, keyspace, and table all exist and that their names exactly match the values in Azure Cosmos DB.

Get Azure table throughput

You can use this action to get throughput settings for a Cassandra table in Azure Cosmos DB. Use it to check per‑table provisioned throughput and plan scaling. Enter the following fields or select using smart values:

• Subscription ID
  Enter the Azure subscription ID that contains the Cosmos DB account. This identifies where the table is hosted.

• Resource group name
  Enter the Azure resource group name that contains the Cosmos DB account. This narrows the search to a specific group.

• Account name
  Enter the Azure Cosmos DB account name. This is the account that holds the Cassandra keyspace and table.

• Keyspace name
  Enter the Cassandra keyspace name that contains the table. Use the exact keyspace name from Azure Cosmos DB.

• Table name
  Enter the Cassandra table name to get throughput for. Use the exact table name as it appears in the keyspace.

If you don’t see the expected throughput, verify that the keyspace and table names are correct and that the table uses its own throughput settings.

List Azure Cassandra clusters

You can use this action to list Cassandra clusters in an Azure resource group. Use it to discover clusters before managing them. Enter the following fields or select using smart values:

• Subscription ID
  Enter the Azure subscription ID that contains the resource group. This identifies where the clusters are hosted.

• Resource group name
  Enter the Azure resource group name to list Cassandra clusters from. This narrows the search to a specific group.

The action returns Cassandra clusters in the specified resource group. If no clusters are found, check that the subscription and resource group values are correct and contain Cassandra resources.

List Azure clusters subscription

You can use this action to list Cassandra clusters in an Azure subscription. Use it to get a cross‑resource‑group view of clusters in one subscription. Enter the following fields or select using smart values:

• Subscription ID
  Enter the Azure subscription ID to list Cassandra clusters from. This is the subscription whose clusters you want to see.

The action returns Cassandra clusters across the subscription. If no clusters are returned, confirm that the subscription ID is valid and that it contains Cassandra resources.

Application Insights Spoke actions

List Azure Application Insights components

You can use this action to list all Application Insights components in an Azure subscription. Use it to discover monitoring resources before querying metrics or telemetry. Enter the following fields or select using smart values:

• Subscription ID
  Enter the Azure subscription ID (GUID) that contains the Application Insights resources you want to list.

The action returns Application Insights components in the subscription. If the action fails or returns nothing, check that you entered a valid subscription ID in GUID format.

Get Azure application telemetry

You can use this action to get telemetry data from Azure Application Insights using Kusto Query Language (KQL). Use it to analyze requests, traces, exceptions, and other telemetry. Enter the following fields or select using smart values:

• Application ID
  Enter the Application Insights application ID (GUID) for your resource. This identifies which app’s telemetry to query.

• Query
  Enter the KQL query to run against Application Insights telemetry data. For example, start with a simple query such as:
  requests | take 50

• Timespan
  Enter the time range for the query as a duration or a start/end range. For example, use PT1H for the last hour or
  2024-01-01T00:00:00Z/2024-01-02T00:00:00Z for a specific period.

You can refine your KQL query and timespan to focus on the telemetry you care about. If the action fails, check that the application ID is valid and that the query and timespan use supported formats.

Get Azure metric

You can use this action to get a specific metric from Azure Application Insights. Use it to track performance, reliability, or custom metrics over time. Enter the following fields or select using smart values:

• Application ID
  Enter the Application Insights application ID (GUID) for your resource. This identifies which app’s metrics to retrieve.

• Metric ID
  Enter the metric identifier to retrieve, such as a standard or custom metric name. For example, requests/count, requests/duration, or exceptions/count.

• Interval
  Enter the time grain for aggregating metric data, such as minutes, hours, or days. For example, PT1M (1 minute), PT1H (1 hour), or P1D (1 day).

• Filter
  Enter an OData filter expression to narrow down metric results. For example, use request/success eq true to limit to successful requests.

• Top results
  Enter the maximum number of metric results to return. Use a small number (such as 10) to keep results focused.

Adjust the metric ID, interval, filter, and top results to shape the data you receive. If the action fails, confirm that the application ID and metric ID are valid and that the interval, filter, and top results use supported values.

Get Azure app component

You can use this action to get details for an Azure Application Insights component. Use it to review configuration and metadata before changing monitoring settings. Enter the following fields or select using smart values:

• Resource group name
  Enter the Azure resource group name that contains the Application Insights component. This narrows the search to a specific group.

• Resource name
  Enter the Application Insights resource name to retrieve. Use the name exactly as it appears in the Azure portal.

• Subscription ID
  Enter the Azure subscription ID that contains the Application Insights component. This identifies where the resource is hosted.

• API version
  Enter the Azure API version to use for this request. You can use the version shown in the Azure REST API docs for Application Insights.

If the action fails, check that the subscription ID, resource group name, resource name, and API version match the values and versions supported in your Azure environment.

Get Azure app events

You can use this action to get events from Azure Application Insights telemetry. Use it to inspect individual events or groups of events over a time range. Enter the following fields or select using smart values:

• Application ID
  Enter the Application Insights application ID (GUID) for your resource. This identifies which app’s events to retrieve.

• Event ID
  Enter the specific event ID to retrieve if you want a single event. Leave this empty to retrieve all events of the selected type.

• Timespan
  Enter the time range for retrieving events as a duration or start/end range. For example, use PT1H for the last hour or P1D for the last day.

• Event type
  Enter the type of events to retrieve, such as requests, pageViews, customEvents, exceptions, or $all to retrieve all types.

You can leave Event ID empty to get all events of a type within the timespan, or supply a specific ID to focus on one event. If the action fails, check that the application ID, timespan, and event type are valid and supported.