Showing content from https://docs.unstructured.io/ui/sources/azure-blob-storage below:
Azure - Unstructured
If you’re new to Unstructured, read this note first.Before you can create a source connector, you must first sign in to your Unstructured account:
- If you do not already have an Unstructured account, go to https://unstructured.io/contact and fill out the online form to indicate your interest.
- If you already have an Unstructured account, sign in by using the URL of the sign in page that Unstructured provided to you when your Unstructured account was created. If you do not have this URL, contact Unstructured Sales at sales@unstructured.io.
After you sign in, the Unstructured user interface (UI) appears, which you use to create your source connector.After you create the source connector, add it along with a destination connector to a workflow. Then run the worklow as a job. To learn how, try out the hands-on UI quickstart or watch the 4-minute video tutorial.You can also create source connectors with the Unstructured API. Learn how.If you need help, reach out to the community on Slack, or contact us directly.You are now ready to start creating a source connector! Keep reading to learn how. Ingest your files into Unstructured from Azure Blob Storage. The requirements are as follows. The following video shows how to fulfill the minimum set of Azure Storage account requirements: If you are generating an SAS token as shown in the preceding video, be sure to set the following permissions:
- Read and List for reading from the container only.
- Write and List for writing to the container only.
- Read, Write, and List for both reading from and writing to the container.
Here are some more details about these requirements:
- An Azure account. To create one, learn how.
- An Azure Storage account, and a container within that account. Create a storage account. Create a container.
- The Azure Storage remote URL, using the format
az://<container-name>/<path/to/file/or/folder/in/container/as/needed> For example, if your container is named my-container, and there is a folder in the container named my-folder, the Azure Storage remote URL would be az://my-container/my-folder/.
- An SAS token (recommended), access key, or connection string for the Azure Storage account. Create an SAS token (recommended). Get an access key. Get a connection string. Create an SAS token (recommended): Get an access key or connection string:
To create the source connector:
- On the sidebar, click Connectors.
- Click Sources.
- Cick New or Create Connector.
- Give the connector some unique Name.
- In the Provider area, click Azure Blob Storage.
- Click Continue.
- Follow the on-screen instructions to fill in the fields as described later on this page.
- Click Save and Test.
Fill in the following fields:
- Name (required): A unique name for this connector.
- Recursive: Check this box to recursively access files from subfolders within the container.
- Remote URL (required): The Azure Storage remote URL, with the format
az://<container-name>/<path/to/file/or/folder/in/container/as/needed> For example, if your container is named my-container, and there is a folder in the container named my-folder, the Azure Storage remote URL would be az://my-container/my-folder/.
- Account Name: For SAS token authentication and account key authentication, the Azure Storage account name.
- SAS Token: For SAS token authentication, the SAS token for the Azure Storage account.
- Account Key: For account key authentication, the key for the Azure Storage account.
- Connection String: For connection string authentication, the connection string for the Azure Storage account.
Responses are generated using AI and may contain mistakes.
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4