Authentication Error When Writing to Blob Storage

General
1

Hello,

I encountered a 403 authentication error when trying to write data to a Blob Storage destination. The issue seems to be related to the authorization header or the validity window in the SAS token.

The token setup looks correct, so I’m wondering if anyone has run into similar issues. It could be related to time sync, signature formatting, or other configuration inconsistencies.

Any insights or recommendations would be really helpful, thank you!

Jorge

2

Hi Jorge,

Hope you’re doing well!

It looks like your flow from Dataddo to Microsoft Fabric via Azure Blob Storage failed due to an expired Shared Access Signature (SAS) token. Based on the error message as I have checked, the token was no longer valid at the time of the attempted access:

Signature not valid in the specified time frame
Start: 07 April 2025
Expiry: 30 April 2025
Attempted access: 15 May 2025

:white_check_mark: How to Fix It

You’ll need to generate a new SAS token with an updated time window and apply it to your Dataddo destination. Here’s how:

  1. Go to your Azure Portal.
  2. Navigate to your Storage Account > Containers > Shared access tokens.
  3. Configure the token with:
  • Permissions: Read, Add, Create, Write, Delete, List, Move
  • Expiry date: We recommend at least 6 months into the future
  • Allowed IP addresses: Leave blank (optional)
  • Allowed protocols: Set to HTTPS only
  1. Copy the Blob SAS token and paste it into the corresponding field in your Dataddo destination configuration.
  2. Save and restart the flow to confirm the issue is resolved.

For a detailed walkthrough, you can refer to our guide here:
:backhand_index_pointing_right: Dataddo Azure Blob Storage Setup Guide

Let us know if you’d like help with any of the steps—we’re happy to assist!

Best,
Sopio