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 one to two minutes to propagate; then drop a PDF and watch redacted/.

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

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.