1. To-Increase Dynamics 365 for Finance & Operations
  2. Connectivity studio
  3. Activities

Set up Blob storage connector
Application task

Set up a connector of type Blob storage to exchange data files between your D365 FO environment and another environment, using Azure Blob storage. Azure Blob storage is Microsoft's object storage solution for the cloud. Blob storage is optimized for storing massive amounts of unstructured data.

With the Blob storage type connector, you can exchange these external file-based documents: EDI, Fixed text, Microsoft Word, Microsoft Excel, Text, XML, JSON. You can only use this connector in combination with a document for which the version 3 (V3) handler class is selected.

You can use one of these authentication methods to access the Blob storage:

 

  • Shared access key: Grants access to a storage account.
  • Shared access signature (SAS): Grants access to a specific Blob container.
  • Client credentials: Grants access to Blob storage via an Microsoft Entra ID application with Azure storage permission.
  • Password: Grants access to Blob storage via an Microsoft Entra ID application with Azure storage permission.
For more information, refer to:

 


Standard procedure

1. Click Connectivity studio Integration Design.
2. Click the Connectors tab.
3. Click New.
4. In the Connector field, type a value.
 

Note: You are advised to not include, in the connector name, the name of the application to which you connect. Use the Application field to define the applicable application for the connector.
5. In the Project field, enter or select a value.
6. Define the applicable application for the connector. For a Blob storage connector, for example, select a 'Blob storage' application.
  In the Application field, enter or select a value.
 

Note:
- You can only select an application that is defined for the applicable project. You can define project applications on the Projects page.
- You can type any existing application name, whether it is defined as project application or not. If the typed application is not defined as project application, it is automatically added to the project applications.
7. In the Connector type field, select 'Blob Storage'.
8. Sub-task: Set properties.
  8.1 You can export connectivity setup and import it in another D365 FO environment. For example, you first set up and test the connectivity setup in a development environment. When finished, you deploy the setup in your production environment. To prevent messing up your production data, use different Blob containers for your development or testing environment and for your production environment. To strictly distinguish between different environments, you can define unique connector properties for each of your environment types. Which properties are applicable to the current environment is defined in the Environment type field on the Connectivity studio parameters. Example: If set to Development, the connector properties as defined for environment type Development are applicable.
  In the Environment types field, select an option.
 

Note: The environment types only apply to connectors of type Database, Azure file storage, Blob storage, SharePoint, or Service Bus queue.
  8.2 Expand the Properties section.
  8.3 In the Blob storage account field, enter the applicable Azure storage account name.
 

Note: Only the Azure storage account name is required here and not the full URL.
  8.4 In the Azure blob container field, enter the name of the applicable Blob container.
 

Note: Only the Blob container name is required here and not the full URL.
  8.5 Define how access to Azure Blob storage is granted:
- Shared access key: Fill in the Password field Password reference field.
- Password: Fill in these fields: Token authorization endpoint, Resource, Client ID, User name, Password or Password reference, and Scope.
- Client credentials: Fill in these fields: Token authorization endpoint, Resource, Client ID, Client secret or Client secret reference, and Scope.
- Shared access signature: Fill in the Password field or Password reference field.
  In the Authentication field, select an option.
  8.6 Enter the password or password reference to access a:
- Blob container if the authentication is 'Shared access signature (SAS)'.
- Storage account if the authentication is 'Shared access key'.
- Blob storage if the authentication is 'Password'.
Whether the password or password reference applies is defined by the Display secret field in the Connectivity studio parameters.
If the Display secret parameter is set to:
- Secret, fill in the Password field with the desired access key or signature. The access key or signature is specific for the current connector.
- Secret reference, fill in the Password reference field with the desired secret reference. The password reference refers to a centrally stored access key or signature which makes updating secrets easier.
- Both, fill in either the Password field or the Password reference field.
  In the Password field, or in the Password reference field, type a value.
 

Note: This field is only applicable if the authentication is 'Shared access key' 'Shares access signature', or 'Password'.
  8.7 Define the base Microsoft Entra ID authority as follows: https://login.microsoftonline.com/[Tenant ID]/
The 'Tenant ID' is your Microsoft Entra ID tenant ID (or directory ID).
The tenant ID identifies the Microsoft Entra ID tenant to use for authentication. It is also referred to as the directory ID. To retrieve the tenant ID, navigate to the Overview page for your app registration in the Azure portal, and copy the value from there.
  In the Token authorization endpoint field, type a value.
 

Note: This field is only applicable if the authentication is 'Client credentials' or 'Password'.
  8.8 Define the applicable Microsoft Entra ID resource ID. The resource ID indicates the audience for which a token that is issued can be used to provide access to an Azure resource. In the case of Azure Storage, the resource ID may be specific to a single storage account, or it may apply to any storage account.
Usually, the resource is: https://storage.azure.com/
  In the Resource field, type a value.
 

Note: This field is only applicable if the authentication is 'Client credentials' or 'Password'.
  8.9 In the Client ID field, enter the Application (client) ID of the registered Microsoft Entra ID application that you use to access the Blob storage.
 

Note: This field is only applicable if the authentication is 'Client credentials' or 'Password'.
  8.10 In the User name field, enter the user name that is used to access the Microsoft Entra ID application that you use to access Blob storage.
 

Note: This field is only applicable if the authentication is 'Password'.
  8.11 Enter the client secret or client secret reference of the registered Microsoft Entra ID application that you use to access the Blob storage.
Whether the client secret or client secret reference applies is defined by the Display secret field in the Connectivity studio parameters.
If the Display secret parameter is set to:
- Secret, fill in the Client secret field with the desired client secret. The client secret is specific for the current connector.
- Secret reference, fill in the Client secret reference field with the desired secret reference. The client secret reference refers to a centrally stored client secret which makes updating secrets easier.
- Both, fill in either the Client secret field or the Client secret reference field.
  In the Client secret field, or in the Client secret reference field, type a value.
 

Note: This field is only applicable if the authentication is 'Client credentials'.
  8.12 For the used Microsoft Entra ID application, Azure Storage permissions are defined. You can use the scope to prompt consent for specific permissions for this connection. For example, user_impersonation.
  In the Scope field, type a value.
 

Note: This field is only applicable if the authentication is 'Client credentials' or 'Password'.
9. Sub-task: Select custom handler.
  9.1 Expand the Custom section.
  9.2 For a Blob Storage type connector, the standard handler class is BisConnectorStreamBlobStorage. This handler class exports data to or imports data from a file in a Blob container. You can use a customized handler class. To do so, extend the standard handler class.
  In the Handler field, you can enter or select a custom handler class.
10. Sub-task: Set advanced options.
  10.1 Expand the Advanced options section.
  10.2 A document can have a query for which cross-company is enabled. If a user, with access to a restricted set of companies, runs a message that uses the document, the cross-company option does not work. If you have this scenario, make sure the cross-company option is enabled for the used connector. Otherwise, you can disable the cross-company option.
  Select Yes in the Cross company disabled field.
11. Close the page.

Notes

If you use a Blob storage connector as source or target connector on a message, make sure the related source or target document uses the 'V3' handler version.

Related to Notes

Set up Blob storage connector

 		 

See also

Provide feedback