Hi @sunil mehta
Thank you for providing more information about your scenario. To access a queue via a Web Activity using a SAS token, you need to ensure that the SAS token has the appropriate permissions to access the queue. Specifically, the SAS token needs to have the "read" permission for the queue. You can generate a SAS token with the appropriate permissions using the Azure Storage Explorer or the Azure Portal.
Regarding the permissions required for ADF, you don't need to give any specific permissions to ADF to access the queue via a Web Activity. However, you need to ensure that the ADF service has network access to the storage account that contains the queue.
If you have confirmed that the SAS token has the appropriate permissions and you are still experiencing issues with accessing the queue via the Web Activity, you may want to check the following:
- Check the URL you are using in the Web Activity to ensure that it is correct and includes the SAS token.
- Check the headers you are using in the Web Activity to ensure that they are correct and that you are not using any headers that are not supported by the Azure queue.
- Check the CORS settings for your storage account queue to ensure that they are configured correctly to allow the HTTP verb you are using in your Web Activity.
If you are still experiencing issues after trying these steps, you may want to check the logs for the Web Activity to see if there are any error messages or warnings that could provide more information about the issue.
I hope this helps you troubleshoot the issue with accessing the queue via a Web Activity using a SAS token. If you have any further questions, please feel free to ask!