Microsoft Azure Blob Storage Spoke

  • Release version: Yokohama
  • Updated January 30, 2025
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Microsoft Azure Blob Storage Spoke

    The Microsoft Azure Blob Storage Spoke enables ServiceNow customers to manage Azure blobs and containers directly from their ServiceNow instance. This integration facilitates automation of Azure Blob Storage tasks through prebuilt actions and sample subflows, helping streamline cloud storage management within ServiceNow workflows.

    Show full answer Show less

    This spoke requires an Integration Hub subscription and depends on several ServiceNow plugins to function correctly. Customers must have an Azure Storage account with the Storage Blob Data Owner role assigned to enable proper access and integration.

    Key Features

    • Sample Subflows: Predefined automations such as moving blobs between containers, renaming blobs, and retrieving lists of blobs or containers. These can be customized by copying into a new application scope.
    • Spoke Actions: Extensive actions for blob and container management, including:
      • Blob Management - attach, copy, delete, lease, lookup, snapshot, and upload blobs.
      • Container Management - create, delete, lease, lookup containers, and release leases.
    • Connection and Credential Aliases: Integration Hub utilizes aliases for managing connections and credentials, simplifying configuration across multiple environments and reducing maintenance when credentials change.

    Practical Requirements and Setup

    • Requires an Azure Storage account with the Storage Blob Data Owner role assigned via Azure portal's Access Control (IAM).
    • Record and save the Azure access keys and Directory ID for integration configuration.
    • Ensure dependent ServiceNow plugins related to IntegrationHub and JSON/REST action steps are installed and licensed as needed.
    • Spoke is built for Azure API version 2023-11-03 and may work with newer versions.

    What Customers Can Expect

    By deploying this spoke, ServiceNow customers gain efficient, automated control over Azure Blob Storage resources within their ServiceNow environment. This integration reduces manual cloud storage management tasks and supports seamless workflow automation related to blob and container operations, improving operational efficiency and governance.

    Manage Azure blobs and containers from your ServiceNow instance.

    Request apps on the Store

    Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.

    Integration Hub subscription

    This spoke requires an Integration Hub subscription. For more information, see Legal schedules - IntegrationHub overview.

    Spoke version

    Azure Blob Storage spoke v2.0.0 is the latest version.

    Spoke dependencies

    If you’re having trouble installing the app, confirm that these dependent plugins are installed:
    • ServiceNow IntegrationHub Action Step - REST (com.glide.hub.action_step.rest)
    • ServiceNow IntegrationHub Action Step - JSON Parser (com.glide.hub.action_step.jsonparser)
    • ServiceNow IntegrationHub Runtime (com.glide.hub.integration.runtime)
    • Complex Object (com.glide.cobject)
    • IHUB Spoke Util Pack (com.snc.ihub_spoke_util_pack)
    Note:
    Some of these plugins are licensable features and require appropriate licenses, if used outside the spoke implementation.

    Supported versions

    This spoke was built for API version 2023-11-03, but may be compatible with later versions.

    Spoke requirements

    • Storage account in your Microsoft Azure portal for integration with your ServiceNow instance.
      Note:
      Verify that you have the Storage Blob Data Owner role.
      To assign the role:
      1. Log in to your storage account and navigate to Access Control(IAM).
      2. Select the Add a role assignment and select the Storage Blob Data Owner role.
      3. Assign access to the required Azure AD user, group, or service principle option. Select the email address of the Azure account and save the changes.

        Add the Storage Blob Data Owner role

      For more information, see Use the Azure portal to assign an Azure role for access to blob and queue data.
    • Record and save the access keys and Directory ID for later use.

    Spoke subflows

    The Azure Blob Storage spoke provides sample subflows to demonstrate automating the Azure Blob Storage tasks. To customize a sample flow, copy it to a new application scope. Available sample flows include:
    Subflow Description
    Move Blob Moves a blob from source container to destination container.
    Rename Blob Renames the specified blob.
    Look up Blobs Stream Retrieves the details of all blobs in a container.
    Look up Containers Stream Retrieves a list of containers under the specified storage account.

    Spoke actions

    The Azure Blob Storage spoke provides actions to automate Azure Blob Storage tasks when events occur in the ServiceNow AI Platform. Available actions include:

    Category Action Description
    Blob Management Attach Blob to ServiceNow Record Attaches a blob to the ServiceNow record.
    Copy Blob Copies a blob from one container to another container.
    Delete Blob Deletes the specified blob.
    Lease Blob Creates a lock on a blob for write and delete operations.
    Look up Blob Retrieves details of the specified blob.
    Look up Blobs Retrieves details of all blobs in a container.
    Release Lease on Blob Releases a lock on a blob.
    Snapshot Blob Creates a snapshot for the specified blob.
    Upload Attachment to Container Uploads a blob in specified container.
    Container Management Create Container Creates a container under the specified account.
    Delete Container Deletes a container.
    Lease Container Creates a lock on the container for delete operations.
    Look up Container Retrieves details of the specified container.
    Look up Containers Retrieves list of the containers under the specified storage account.
    Release Lease on Container Releases a lock on a container.

    Connection and credential alias requirements

    Integration Hub uses aliases to manage connection and credential information, and OAuth credentials. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you don't need to update any actions that use the connection.

    For information about setting up the spoke, see Set up the Microsoft Azure Blob Storage Spoke.