Resolving Access Issues: Azure Function App Proxy with Private Blob Container - Need Configuration Guidance

I'm seeking advice on how to configure my Azure Function App to properly authorize users and direct them to a Static Web App hosted in a private Blob Container. The goal is to ensure seamless access without enabling public access on the Blob Container.

Scenario Overview:

• Setup: A Function App serves as a proxy for a Static Web App stored in a Blob Container.
• Blob Configuration: The Blob Container is set to private access.

What Works:

• With public access enabled on the Blob Container, everything functions correctly.
• Authentication and App Registration have been configured and work flawlessly.

The Problem:

• When public access to the Blob Container is disabled, the setup fails, returning a "resource not found" error.

Efforts Taken So Far:

• Configured Managed Identity for the Function App and granted necessary permissions to the Blob Container.
• Confirmed the proxy functions correctly with public access enabled.

Current Behavior:

• Public Access Enabled: Everything works fine.
• Public Access Disabled: Access fails with the error "resource not found."

Key Questions:

1. Do I need additional configurations in the proxy definition file?
2. Should I implement a private endpoint or another specific setting to address this issue?

Additional Notes:

I haven't configured a private endpoint yet but am considering it. My expectation was that Managed Identity permissions would suffice, but it seems something more is needed.

Request:

Any guidance or suggestions on how to resolve this issue would be greatly appreciated!