On demand · Product video
Set up Azure Blob Storage and Document Intelligence for Quality Inspector
For administrators who want to scan paper inspection forms and pictures into quality tests.

Summary
This video sets up the Azure services that Quality Inspector uses to read paper forms and pictures. In the Azure portal, it creates a storage account, allows anonymous blob access, adds a container, and generates a shared access signature (SAS) token, then enters all three in Quality Inspector setup. It then creates an Azure Document Intelligence resource (formerly Azure Form Recognizer) and copies its endpoint and key into the same setup. To test the connection, it builds a template by detecting fields from a picture, prints an inspection report, fills it in by hand, and scans it with the camera so Quality Inspector fills in the test values.
Key topics
- Create an Azure storage account, container, and SAS token
- Connect Azure Document Intelligence with its endpoint and key
- Detect template fields from a picture of a form
- Scan a completed paper form to fill in test values
Read the transcript
In this video, we’re going to review how to create an Azure Blob Storage account, an Azure Blob Storage container, and a SAS token, which is a shared access signature, as well as an Azure Document Intelligence instance, which was previously known as Azure Form Recognizer. So let’s get started. First, you need to head to portal.azure.com. In here, we’re going to go to Storage accounts. Now we’re going to create a new storage account, and I’ll just give it a name.
Now, if you’re following along, you’re not going to be able to use this exact same name. This resource will be deleted when this video is done, but you will be able to create your own. And because these names are global, you should choose a name that’s unique to your specific install. All right, so we’re going to click Review and then Create, and wait for this storage account to finish. Okay, it looks complete, so now we’re going to go to our resource.
In here, the first thing we need to do is allow anonymous access for blobs. This is in the Configuration section underneath Settings. We’re going to choose Enabled and then Save. This setting can take up to a minute to take effect, so we’re going to wait before moving on to the next step. All right, I’m going to choose Refresh to make sure that the setting has taken effect. It has.
The next step is to create a container. So we’re going to navigate to Containers and create a new container. If you want, you can give it the same name, but it can have a different name. And again, if you’re following along, this container is not going to exist at the end of this video, so you won’t be able to use this exact container name. We’re going to choose container access, or if you want, you can also choose blob access. So we’re going to create that.
All right, so far we have an Azure Blob Storage account, and in there we have an Azure Blob Storage container. The next step is to get a SAS token, a shared access signature. So we navigate into the container, go into Shared access tokens, and create a new token. The permissions that we need are create, write, and delete. If you’re troubleshooting, you should consider adding list as well, as this will let you list any blobs or blob containers you’ve created with that same shared access signature.
The start and end are specific to the time range that you want to allow for this shared access signature. I’m going to set mine to expire a few hours from now. And again, if you’re following along, this token won’t work for you; you’re going to need to create your own. All right, so we generate the SAS token and URL, and we’re just going to copy this token for later. Copy and paste it somewhere secure, because we’re going to use it immediately in the Quality Inspector setup.
So let’s configure what we’ve got so far in Quality Inspector. We navigate back to Business Central, and in the storage account field we put in the storage account that we just created. The container name is the container that we just created, so we navigate back, go to our containers, and give it the same name. And then the token that we just created, we paste in here.
All right, so we’ve just finished the storage configuration. This part is used when you’re uploading an image or a document to be analyzed with Azure Document Intelligence. Quality Inspector uses the token, the container, and the storage account here both to create the image temporarily and to delete it when it’s done. That information is then passed to Azure Document Intelligence, and that’s the next step we’re going to configure.
So now we navigate back to portal.azure.com and go to Document Intelligence. We’re going to create a new Document Intelligence resource and give it the same name we just used, although it can be any name. If you’re just trying out the system, or if you don’t have a lot of pages to scan, you should have access to the free tier. This is 500 pages per month or 20 calls per minute, which is good enough for most demonstration or training systems. Once you’ve exceeded that, Azure has another pricing tier that allows more calls.
For now, we’re just going to choose the free one. If you don’t see the free tier, it’s possible you already have another Document Intelligence instance, since you’re only allowed to have one free Document Intelligence instance deployed. So we’re going to review and create this, and wait for it to deploy. All right, it’s finished deploying.
So now we go to the resource, and inside Azure Document Intelligence we’re going to see Keys and Endpoint. Where it says Endpoint, we’re going to copy this, and in the Quality Inspector setup we paste it into the endpoint field. We navigate back again and copy the key. It doesn’t matter which one you use, key 1 or key 2. We paste it into the key field here.
The model can be left blank, and in most circumstances this does a pretty good job of analyzing most documents. If you’re having trouble analyzing your documents, you can create a specific model in Azure Document Intelligence that is trained for your specific quality inspection forms, and then put the model name here. If you don’t have that, or if you’re just configuring a demonstration system, you can leave the model blank.
Okay, so the next step is to test this and make sure it’s all connected. There are two features we’re going to use to test this. The first is to scan a document to make sure it can read the fields and create a template from that. Then we’re going to scan in the same document and fill out the values. To do that, we close this and head over to the templates. We create a new template and connect it to any table in the system. We’ll just use the item ledger entry for now.
All right, so now let’s add fields to this template. We choose to add fields, then Detect fields from a picture, and choose Next. Then we put in this image file. It’s a very basic scenario with some example text: we’re capturing the height, the length, the width, and the weight. It looks like it’s finished, so in here we choose which fields we want to include: the height, the length, the width, and the weight. Then we choose Finish. Now we have a quality inspection template with the fields from an existing test document.
Next, we’re going to create a test so we have an actual quality inspection test, and then we’re going to print it. We choose a record; for this example, we’re just choosing any sample data. So now we have our quality inspection test with height, length, width, and weight. We’re going to simulate filling this out as a person and then scanning it in. To do that, we use the inspection report, and we print it. Okay, so I’ve filled in the values by hand, and now we’re going to scan that in.
To do that, we navigate to the scan page, and we’ve got two options. If you already have the picture uploaded, similar to what we did with the templates, you can use it that way. Alternatively, you can scan it directly with the camera, and that’s what we’re going to do. We allow Business Central to use the camera. There’s our document, and we use that picture. We assign the test to ourselves.
Now it’s uploading the image to Azure Blob Storage, and once it has that image, it sends it over to Document Intelligence, which detects the values. We can see it does a pretty good job: it found the 34, the 40, the 52, and the 63. It had a small issue with these, so we’re just going to remove that and choose OK. Now we can see the values filled in. When you use the option to take a picture, it’ll also be saved as a document attachment.
All right, so this was an end-to-end example of how to set up and configure an Azure Blob Storage account, an Azure Blob Storage container, and a Document Intelligence instance, how to use those values in Quality Inspector, and how to use the key Document Intelligence features inside Quality Inspector.
Questions about this webcast?
Send your question and the Insight Works team will reply by email. Ready to plan a project? Contact your Microsoft Partner.
Ask a question
More recordings
Webinar recording · 38 minBusiness Central quality is a starting point: Here’s how partners take it furtherQuality InspectorRecorded May 2026
Webinar recording · 60 minTransform your quality assurance process with Dynamics 365 Business CentralQuality InspectorRecorded February 2026
Product video · 6 minCollect quality test values in Microsoft Teams with adaptive cards in Quality InspectorQuality InspectorRecorded December 2025