---
title: "Set Up and Configure Azure Blob Storage and Azure Document Intelligence with Quality Inspector"
app: "Quality Inspector"
section: "Set up"
last_updated: "2026-09-22"
url: "https://insight-works.com/kb/quality-inspector/set-up-and-configure-azure-blob-storage-and-azure-document-intelligence-with-quality-inspector/"
---

# Set Up and Configure Azure Blob Storage and Azure Document Intelligence with Quality Inspector

Note: This feature requires Business Central 23 or newer.

The Azure Blob Storage is configured is only used with the “Scan Page With Camera” and “Scan Page With Upload” feature on Quality Inspection Test documents, and the “Detect fields from a picture” when using an existing scan or picture of a Quality Inspection Document to configure fields. It is used specifically to:

- Either take a picture with your camera, or upload an existing image of the document to azure blob storage
- Use Azure Document Intelligence (Form Recognizer) to read and parse the Quality Inspection Document
- Then the image of the inspection document will be removed
- The parsed values will then be applied to either the Quality Inspection Test document (if using “Scan Page With Upload”, or “Scan Page With Camera”), or to add proposed fields (if using the “Detect fields from a picture” feature).
- The blob is not retained.
- The picture of the scanned inspection document that you took is likewise also not retained in either Azure Blob Storage, nor attached documents, nor record links.

You can scan pictures with the “Take Picture”, or upload pictures directly to a Quality Inspection Test, and they will be retained in the Document Attachments. “Take Picture” will not use Azure Blob Storage described on this page to store the miscellaneous pictures. When using add-ons such as DocXtender however those pictures can be stored on SharePoint.

“Take Picture” will take a picture, and attach the picture to the Quality Inspection Test document, it does not use Azure Blob Storage.

“Scan Page With Camera” and “Scan Page With Upload” will take a picture of a document, temporarily use Azure Blob Storage, analyze the blob with Azure Document Intelligence, delete the Azure Blob, and then fill in the values on the Quality Inspection Test Document, but it will not add the picture to the attachments, and the azure blob that was created temporarily will be deleted.

If you are just taking pictures and attaching them to Quality Inspection Test then you do not need to configure Azure Blob Storage.

If you want to take a picture of a printed inspection document to fill in values using Azure Document Intelligence, with that image not being retained, then you do need to configure Azure Blob Storage, and that blob will only be used temporarily until Azure Document Intelligence is done analyzing the picture of the document.

Use this guide to perform the necessary configuration to allow scanning a picture of paper documents or scanning documents into quality inspection documents in Business Central.  This article is the setup and configuration guide related to the user guide: [https://kb.dmsiworks.com/knowledge-base/how-to-scan-paper-quality-inspection-forms-into-quality-inspector/](/kb/quality-inspector/how-to-scan-paper-quality-inspection-forms-into-quality-inspector/)

_Set Up and Configure Azure Blob Storage and Azure Document Intelligence with Quality Inspector_ shows you how to configure and deploy an Azure BLOB Storage account, an Azure BLOB Storage container, generate an SAS token and deploy an Azure Document Intelligence instance, and then connect those values in Quality Inspector.

Complete the following sections in order:

1. Create Azure storage account, enable anonymous Blob access, and create container
2. Create SAS token
3. Create Azure Document Intelligence (Azure Form Recognizer)
4. Test the configuration in Quality Inspector

### Create Azure storage account, enable anonymous Blob access, and create container

1. Navigate to Microsoft’s _[Azure Portal](https://portal.azure.com/)_ in a web browser.
2. Select **Storage accounts** and select **+Create** (or**Create storage account** if needed).
3. Modify the following fields:

   - Subscription
   - Resource Group
   - Storage account name
   - Region
   - Performance
   - Redundancy
4. Select **Review** and ensure the information is correct.
5. Select **Create** (deploys the account).
6. Select **Go to resource**.

 Note: _Redundancy_ is unnecessary; Azure Blob storage images are temporary. For more information, see Microsoft’s _[Create a storage account](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-create)_.

1. Select **Configuration** in the left pane.
2. Enable _Allow Blob anonymous access_, select **Save**(may take a minute to take effect), and select **Refresh**.
3. Select **Container** in the left pane.
4. Select **+Container** and modify the following fields:

   - Name
   - Anonymous access level: Container (anonymous read access for containers and blobs)
5. Select **Create** (redirects to list of containers).

 Note: Due to an Azure Document Intelligence restriction, Anonymous Blob Access is required as any image used must be a public facing image. To increase security to work around this limitation, use an SAS token.

### Create SAS token

 Note: Treat your SAS token like a password; do not publicize your token.

1. Select **Shared access tokens**.
2. Select _Permissions_ dropdown and enable:

   - Read
   - Add
   - Create
   - Write
   - Delete
   - List
3. Select _Start_ date and time, and select _Expiry_ date and time.
4. Select **Generate SAS tokens and URL**.
5. Copy and paste the following information from Azure to the corresponding fields in Quality Inspector:

   - Storage account name (on the storage account page)
   - Storage container name (on the container page)
   - SAS Token (on the _Shared access tokens_ / _Overview_ page)

### Create Azure Document Intelligence (Azure Form Recognizer)

1. Navigate to _Document Intelligences_ in Azure.
2. Select **+Create** and modify the following fields:

   - Subscription
   - Resource group
   - Name
   - Pricing tier
3. Select **Review + create** and ensure the information is correct.
4. Select **Create** (deploys).
5. Select **Go to resource** / **Keys and Endpoint**.
6. Copy and paste the following fields from Azure to the corresponding fields in Quality Inspector:

   - Endpoint
   - Key 1 (_Key 1_ or _Key 2_ to the _Key_ field in Quality Inspector)

 Note: The _Model_field, in the _Quality Inspector Setup_ page in the Business Central window, can be left blank for demos or testing. If you plan on using this in a production facility, you can create custom models, specific to your expected forms, inside the Document Intelligence Studio.

### Test the configuration in Quality Inspector

1. Navigate to Business Central and select **Quality Inspector** /**Templates and Rules** / **Test Templates**.
2. Select **+New** and modify the following fields:

   - Code
   - Description
3. Select **Test Generation Rules,** select the _Table_ field, and select an object.
4. Select **OK**.
5. Repeat the previous 2 steps as necessary until you have all your required test rules.
6. Select the back arrow and select **Add Field(s) To This Template**.
7. Enable _Detect fields from a picture_ and select **Next**.
8. Select **click here to browse**(or use the drag and drop feature), locate the required image (image files and PDFs are accepted), and select **Open**.
9. Select the required fields and select **Finish**.
10. Select **Create Test**, select the required _Source_, and select **OK**.
11. Select the required _Choose Record_ and select**OK**.
12. Select **OK**.
13. Select **Actions** / **Analyze Scanned Form** and reupload the same image used previously.
14. Select **OK** / **Yes**.

### Easy Setup Guide: Azure Blob Storage & Document Intelligence for Quality Inspector

[Video: Easy Setup Guide: Azure Blob Storage & Document Intelligence for Quality Inspector](https://www.youtube.com/watch?v=46stUtml_XU)
