Hello Team,
First, a side note:

Can we please get some information in regards to this issue?
And when would we be expecting a fix.
Thanks,
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Hi @saifbadran9 , thank you for the detailed question. We are currently investigating and will update you when we have accurate information to provide.
Hello @saifbadran9, did you see any errors when you tried to cd into the files? You can try running the AzFileDiagnostics script for Windows to detect what might be the issue. Also, could you please check if you have access to the storage account?
Hi @Grace, thanks a lot for following-up on this, and apologies for the delay in response.
Actually, no errors were seen, it just does not cd into the directory (stays on the same directory).
Anyways, we have been informed that this is a known platform issue related to Windows containers and shared storage, and it is fixed and being deployed globally (ETA: late December).
Thanks a lot for taking the time to look into this!
Only one thing related to the document, is to specify that Windows Containers, unlike App Service on Linux, is limited to Azure Files, and does not support Azure Blob.
Thanks for the update @saifbadran9! I have submitted a PR to update the doc, the change will soon be merged internally and should go-live in the public docs shortly.