AmeRedact

Support

Email
abiola@chosenhomeland.com
Response time
Next business day (Pacific time). Installation issues for new customers are handled the same day where possible.
What to include
Your Azure subscription ID, the managed application name, the region, and — if a document did not process — the file name and the time you uploaded it. Please do not email document contents.
Status
Engine operational logs are available to you in your own subscription under the managed resource group's Function App → Log stream.

Before you install

After you install: the one-time grant

AmeRedact never asks for a storage key. Instead, the engine has its own identity, and you give that identity permission to read drop and write redacted and manifest. The deployment's Outputs tab shows the identity's principal ID and the exact commands. In Azure Cloud Shell (PowerShell) or a local shell with Azure CLI:

az role assignment create --assignee-object-id <functionPrincipalId> --assignee-principal-type ServicePrincipal `
  --role "Storage Blob Data Owner" --scope <storageAccountResourceId>
az role assignment create --assignee-object-id <functionPrincipalId> --assignee-principal-type ServicePrincipal `
  --role "Storage Queue Data Contributor" --scope <storageAccountResourceId>

Or run the provided grant-storage-access.ps1 with the two values from the Outputs tab. Role assignments take a few minutes to propagate. Files dropped before that are picked up automatically on the next scan — no need to re-upload.

You can revoke access at any time by deleting those two role assignments. The engine will stop processing immediately and nothing else changes.

Working with your files

You can use the Azure portal, but most practices prefer Azure Storage Explorer — a free desktop app from Microsoft that lets you drag whole case folders in and out of your storage account. One-time setup:

  1. Give yourself data access. Your Azure sign-in needs the Storage Blob Data Contributor role on the storage account (subscription Owner alone is not enough for file access). The prerequisites script below does this for you; or Storage account → Access control (IAM) → Add role assignment.
  2. Install Storage Explorer from azure.microsoft.com/products/storage/storage-explorer (Windows and macOS) and sign in with the same Azure account.
  3. Open your account: Subscription → Storage Accounts → your account → Blob Containers → drop.
  4. Drag PDFs — or whole folders — into drop. Folders are preserved: drop/CASE-001/01_ER.pdf produces redacted/CASE-001/01_ER.pdf.deid.txt, and every file in the same case folder shares one date-shift offset.
  5. Collect results from redacted (de-identified text + audit JSON) and check processing status in manifest. Files appear within about a minute of upload.
Azure Storage Explorer showing a PDF in the drop container
1. A PDF dropped into drop with Storage Explorer.
Azure Storage Explorer showing the de-identified text and audit JSON in the redacted container
2. About a minute later: .deid.txt and .audit.json in redacted.

Prerequisites in one paste

Before installing from Azure Marketplace, open Azure Cloud Shell (PowerShell), download setup-prerequisites.ps1 and run it with your own names. It creates the storage account in the right region, the drop container, and the role for your sign-in. After the install, run it once more with -FunctionPrincipalId from the deployment Outputs to grant the engine. Everything it creates is yours.

.\setup-prerequisites.ps1 -ResourceGroup medrecords-rg -StorageAccountName yourfirmphi01 -Location westus3

Known limits

Removing AmeRedact

Delete the managed application from the Azure portal. Azure removes the managed resource group and everything in it. Your storage account, your documents and your de-identified output are untouched. Delete the two role assignments if you want to tidy up.