| 1. | Click Connectivity studio Integration Design. |
| 2. | Click the Connectors tab. |
| 3. | In the list, find and select the desired connector of type Azure file storage. |
| 4. | Click Edit. |
| 5. | 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 file locations for your development or testing environment and for your production environment. To strictly distinguish between different environments, you can define unique file action properties for each of your environment types. So, each file action can have a different set of properties for each applicable environment type. Which file action 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 file action properties, as defined for environment type Development are applicable. |
| In the Environment types field, select an option. | |
|
Note: For each file action, you can repeat the sub-tasks for each of your environment types. To set the environment-specific properties of a file action, only change the environment type, find the file action, and set the properties. So, do not create a new file action for each environment type. |
|
| 6. | Expand the File action section. |
| 7. | Sub-task: Set up an Azure BLOB Storage file action with direction Source. |
| 7.1 | Click New. |
| 7.2 | In the Name field, type a value. |
| 7.3 | In the File action field, select 'Azure blob storage'. |
| 7.4 | Click Save. |
| 7.5 | Define the name of the file to be moved from the Azure BLOB container to the Azure file share. You can use filtering symbols. Example: CustGroup*.txt. |
| In the File name field, type a value. | |
| 7.6 | You can (temporarily) disable a flow action. Example: In a test setup, the setup to do the file action is not available. To prevent errors during test runs of the message, you disable the file action. In this way, you do not have to change or delete the file action. |
| Select Yes in the Skip field. | |
| 7.7 | To access the Azure BLOB container, enter the applicable Azure storage Account name. |
| In the Account name field, type a value. | |
| 7.8 | To access the Azure Blob container, enter the access key or access key reference of the applicable Azure Storage Account. Whether the access key or access key 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 Account key field with the desired access key. The access key is specific for the current file action. - Secret reference, fill in the Account key reference field with the desired secret reference. The account key reference refers to a centrally stored access key which makes updating secrets easier. - Both, fill in either the Account key field or the Account key reference field. |
| In the Account key field, or in the Account key reference field, type a value. | |
| 7.9 | Enter the name of the applicable Azure BLOB container. |
| In the Container name field, type a value. | |
| 8. | Sub-task: Set up an Azure BLOB Storage file action with direction Target. |
| 8.1 | Click New. |
| 8.2 | In the Name field, type a value. |
| 8.3 | In the File action field, select 'Azure blob storage'. |
| 8.4 | Click Save. |
| 8.5 | In the Direction field, select 'Target'. |
| 8.6 | Click Save. |
| 8.7 | You can (temporarily) disable a file action. Example: In a test setup, the setup to do the file action is not available. To prevent errors during test runs of the message, you disable the file action. In this way, you do not have to change or delete the file action. |
| Select Yes in the Skip field. | |
| 8.8 | To access the Azure BLOB container, enter the applicable Azure storage Account name. |
| In the Account name field, type a value. | |
| 8.9 | To access the Azure Blob container, enter the access key or access key reference of the applicable Azure Storage Account. Whether the access key or access key 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 Account key field with the desired access key. The access key is specific for the current file action. - Secret reference, fill in the Account key reference field with the desired secret reference. The account key reference refers to a centrally stored access key which makes updating secrets easier. - Both, fill in either the Account key field or the Account key reference field. |
| In the Account key field, or in the Account key reference field, type a value. | |
| 8.10 | Enter the name of the applicable Azure BLOB container. |
| In the Container name field, type a value. | |
| 9. | Close the page. |
| Related to | Notes |
|---|---|
|
Set up file actions for Azure file storage connector |