Support
Welcome to WalkMe support

Please login in order to continue:

Work flows better with WalkMe
Work flows better with WalkMe.

Outgoing Azure Blob Integration

Last Updated May 31, 2024

Brief Overview

The outgoing integration of WalkMe with Azure Blob enables you to utilize Azure as your primary cloud provider to seamlessly transfer data from the WalkMe platform directly to Azure Blob storage. This facilitates flexibility in data consumption and further integration with in-house BI tools.

Set Up an Outgoing Integration with Azure Blob

Step 1: Access the Integrations page in Insights Classic

  1. Navigate to Insights Classic: https://insights2.walkme.com/
  2. Select the system you would like to setup the integration on from the Monitored Systems widget
  3. Click the Integrations tab in the sidebar
  4. Click Azure Blob under Outgoing Scheduled Integrations

5. Click the NEW INTEGRATION button to get started

Step 3: Create a Destination

The next step is to create a destination in Azure Blob. Meaning, where to store the file you are going to export from WalkMe.

This step can be also performed during Step 3 when adding a new integration.

Information needed to enter:

  • Destination Name: A name to recognize the destination
  • Account Name: The name of the relevant Storage Account in Azure Blob
  • Container Name: The name of the relevant container within the Storage Account in Azure Blob
  • Authentication Method: Select a secure  authentication method to verify user or system identity when accessing Azure Blob storage
    • If SAS (Shared Access Signature) Token is selected, you will be promoted to enter the following:
      • SAS Token = the SAS token generated for the relevant Storage Account
    • If Microsoft Entra ID is selected, you will be promoted to enter the following:
      • Client ID = a unique identifier assigned to your application by Azure Active Directory to recognize it during the authentication process
      • Client Secret = a confidential key or password used by your application in conjunction with the Client ID to authenticate itself to Azure Active Directory
      • Tenant ID = a unique identifier for your organization's instance of Azure Active Directory, specifying the directory in which your application is registered and authenticated

** The “Container Path” is an optional field.

Step 3: Add New Integration

Adding a new integration can be completed in 2 simple steps:

  1. Define Report → Choose the report's name and the origin environment from which you intend to export the data
    • You should also select the desired reporting frequency and determine whether it should be set up as a recurring process
  2. Set Destination → Define a new destination or select a destination from a list.
    • Selecting a destination from the list will auto populate the rest of the information
The report will be sent in CSV format.

Set Up a Microsoft Azure Account and Blob Container

Sign Up for Microsoft Azure

  1. Go to the Microsoft Azure website
  2. Click on "Start free" or "Sign up" to create a new Azure account

Create a Storage Account

  1. Once you have an Azure account, log in to the Azure portal
  2. Click on "Create a resource" and search for "Storage account"
  3. Follow the prompts to create a new storage account
  4. Choose a unique name for your storage account and configure other settings as needed

Create a Blob Container

  1. After creating a storage account, open it in the Azure portal
  2. In the left-hand menu, under "Data storage" click on "Containers"
  3. Click "+ Container" to create a new container
  4. Choose a unique name for your container, configure access level settings, and create the container

Authentication Method

Create a SAS (Shared Access Signature) Token

To interact with your Azure Blob Storage, you'll need to generate a Shared Access Signature (SAS) token.

  1. In the Azure portal, navigate to your storage account and select "Security + networking" > "Shared access signature"
  2. Configure the desired permissions, expiration date, and other settings for your SAS token
  3. Click "Generate SAS and connection string"
  4. Copy the generated SAS token and connection string to share with your service for accessing the container
  • Allowed Services → Blob
  • Allowed Resource Type → Object
  • Allowed Permissions → Read, Write, Delete
  • Blob Versioning Permissions → Leave empty
  • Allowed Blob Index Permissions → Leave empty
  • Start and Expiry Date/Time → Subject to your discretion
  • Allowed IP Addresses → Leave empty
  • Allowed Protocols → HTTPS only
  • Preferred Routing Tier → Basic (default)
  • Sining Key → Key1

Was this article helpful?

Thanks for your feedback!

Be part of something bigger.

Engage with peers, ask questions, share ideas

Ask the Community
×