Azure Blob Connector Prerequisites

User Accounts and Application Permissions

Required Permission	Description
Azure	The installation user account must be able to register, configure, and grant Access for an Azure application.
Azure App Permissions	The application configured for the connector must have the following Graph API permissions granted in Microsoft Azure: Note: The type for the following permissions must be "Application". Delegated permissions are not required. Directory.Read.All GroupMember.Read.All Member.Read.Hidden User.Read.All
Azure Blob Storage	Multiple Permissions The application configured for the connector must be granted the following permissions (otherwise use the "Single Role" detailed below): Microsoft.Storage/storageAccounts/read Microsoft.Storage/storageAccounts/blobServices/read Microsoft.Storage/storageAccounts/blobServices/generateUserDelegationKey/action Microsoft.Storage/storageAccounts/blobServices/containers/read Microsoft.Storage/storageAccounts/blobServices/containers/blobs/tags/read Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read Microsoft.Storage/storageAccounts/blobServices/containers/blobs/filter/action This can be achieved by creating a custom role in Azure (see Microsoft documentation) and assigning it to your configured application. Single Role Alternatively, for a faster implementation, assign your application the Storage Account Contributor role. These are the minimal permissions (or role) necessary to properly extract and report metadata Provides context with details such as the source, type, owner, and relationships to other data sets. Metadata provides details around the item being crawled by Connectivity Hub. and security/ACLs on the blobs indexed.
Windows	The account used to run the connector must be a local Administrator on the server and cannot be any of the built-in service accounts (NetworkService Local account used by the service control manager. Not recognized by the security subsystem, so you cannot specify its name in a call to the LookupAccountName function. Has minimum privileges on the local computer and acts as the computer on the network., local machine, etc.)

Connector Features and Requirements

Features	Supported	Additional Information
Searchable content types	Yes	All content types.
Content Update	Full and Incremental	All BA Insight Connectors support both Full and Incremental crawls, unless noted.
Permission Types	Yes	All BA Insight Connectors support fetch ACLs from the source system Your Source System is the repository where your data is stored (data to be indexed). This repository is managed by applications such as: - SharePoint O365 - SharePoint 2013/16/19 - Documentum - File Share - OpenText - Lotus Notes - etc. Your Source System repository can also be a database such as SQL or Oracle.. To make items *public* or *restricted* to a single user/set of users, you can do so within the Connector Framework.
Required Software	IIS .NET Framework v4.7.2	ASP.Net must be enabled
Connectivity Hub Version	v2.2 or newer	Azure Blob Connector requires Connectivity Hub version 2.2 or newer in order for all features to work properly.