There is actually no durable concept of a container. In other words, there is no need to pro-actively create a container. You can instead just start using it. It would be ideal to create 'token’s for each of these customers that are scoped to the container name designated for the customer. The created token can be stored alongside the customer’s data and then used on their behalf to manage webtask’s scoped to that container.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.