Create Azure blob containers
Important
Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Appsprovides some guidance on moving your integration solutions to Logic Apps.
If you're brand new to Logic Apps, then we suggest getting started here:
-
Create your first logic app, or quickly get started using a pre-built template
-
View all the available connectors you can use in your logic apps
In this topic, we create Azure Blob containers that are required for the solution. We create three containers, one to receive purchase order data before it is sent to the EDI send pipeline, one to receive purchase order data after it is processed by the EDI send pipeline, and one to receive invoice data from Fourth Coffee. We also generate the Shared Access Signature (SAS) URLs to access the blobs. The SAS URL is required for authentication while writing data to the blob.
To create Azure blob containers
Create an Azure storage account as described here: Create an Azure Storage Account. For this tutorial, name the storage account at cloudcardemostore.
Create a container called purchaseorder within the cloudcardemostore storage account. This container will store the purchaser order data received from customers. Create a container by performing the following steps:
On the Azure classic portal, select STORAGE, and then select cloudcardemostore. In the cloudcardemostore dashboard, select CONTAINERS, and then from the command bar, select ADD.
On the New Container dialog box, enter the name as purchaseorder and mark access as private.
Select the check mark to create the container.
Repeat this step to create two more containers and name them invoice and tosupplier.
Create a Shared Access Signature (SAS) for all the containers. SAS is required for authentication while writing data into the container. For instructions on how to generate the SAS, see Create and Use a Shared Access Signature. You can also use the Azure Storage Explorer to generate SAS. For more information about the Azure Storage Explorer, see Azure Storage Explorer.