What Changed
The Azure Functions PowerShell managed dependency for the DocuSign Security Events connector has been bumped from Az 5.* to Az 11.* in requirements.psd1.
Security Impact (Visibility & Fidelity)
Any deployment of this connector running on the Azure Functions PowerShell 7.2+ runtime has been experiencing complete module load failures since installation or upgrade to that runtime. The affected cmdlets – Connect-AzAccount, New-AzStorageContext, and Get-AzStorageBlob – are all required for the connector core ingestion loop. Without them, the Function App timer trigger exits before any DocuSign Monitor REST API calls are made.
Effect: Zero DocuSign security event data ingested into the Log Analytics workspace for affected deployments. This is a complete ingestion blind spot, not a partial fidelity issue.
Per PR discussion, a reviewer noted the ZIP package inside the connector directory also needs the updated run.ps1 – confirm the deployed package matches this fix, as the in-repo file update alone does not redeploy the running Function App.
Remediation Notes
- Update the requirements.psd1 in your deployed Function App to reference Az 11.*.
- Redeploy the Function App package to ensure the runtime picks up the new dependency manifest.
- Validate connector health by confirming Connect-AzAccount succeeds in the next timer trigger execution.
Affected Files
DataConnectors/DocuSign-SecurityEvents/AzureFunctionDocuSignMonitor/DocuSignMonitorTimerTrigger/run.ps1
DataConnectors/DocuSign-SecurityEvents/AzureFunctionDocuSignMonitor/requirements.psd1
DataConnectors/DocuSign-SecurityEvents/CHANGELOG.MD