Private Endpoint, Data Connect and Blob Storage

Receiving 403 error when my pipeline reads from DataConnect and saves into Blob.

{
"errorCode": "2200",
"message": "ErrorCode=UserErrorOffice365DataLoaderError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Office365 data loading failed to execute. office365LoadErrorType: PermanentError. Operation on target 67a42e0a-145a-495c-9cb6-103d5c556609_Activity failed: ErrorCode=AzureBlobFailedToCreateContainer,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Unable to create Azure Blob container. Endpoint: 'https://gbusmgdcconvlineage01.blob.core.windows.net/', Container Name: 'managers'.,Source=Microsoft.DataTransfer.ClientLibrary,''Type=Microsoft.WindowsAzure.Storage.StorageException,Message=The remote server returned an error: (403) Forbidden.,Source=Microsoft.WindowsAzure.Storage,StorageExtendedMessage=RequestId:0b5d4c5a-801e-0012-7e4d-00367a000000 Time:Mon, 16 Oct 2023 16:25:27 GMT,,''Type=System.Net.WebException,Message=The remote server returned an error: (403) Forbidden.,Source=System,',Source=Microsoft.DataTransfer.ClientLibrary,'",
"failureType": "UserError",
"target": "M365ManagersToAZBS",
"details": []
}

I know my Private endpoints are correct, synapse can test connectivity and I can create a simple copy job but when reading from data connect then writing to blob i get this.

Are these technologies not compatible? Is there a work around?

Start with the failed pipeline activity that reads from Data Connect and writes to Azure Blob Storage, then compare it with the simple copy job that succeeds. Review the reported 403 error, private endpoint configuration, and Synapse connectivity results. Done means establishing whether this combination is supported and documenting a confirmed workaround or a reproducible compatibility finding.