I'm an IT professional at a small company that relies heavily on Microsoft 365 and SharePoint but has limited Azure experience. I want to host an interactive, static HTML dashboard using Azure Blob Storage and display it from a SharePoint page. A Power Automate flow would periodically replace the dashboard's index page with an updated version.
The main concern is security. Blob Storage static website URLs are publicly reachable, and I need to prevent unauthenticated access from the internet. Our users work remotely, often from changing home or field IP addresses, so IP allowlisting is impractical. Requiring everyone to connect through a corporate VPN would also create a significant support burden across several hundred laptops.
I looked at Azure Front Door/CDN with Private Link, but it seems to address private connectivity between services rather than providing straightforward authenticated access for remote users. Is there a practical way to protect this dashboard with Microsoft Entra ID or another identity-based solution while still letting users open it through SharePoint in a browser? Would Azure Static Web Apps or App Service be a better fit than Blob Storage, or would embedding the content directly in SharePoint be simpler?
4 Answers
If the dashboard needs to remain a separate web application, Azure Static Web Apps supports Microsoft Entra authentication and is designed for static front ends. That gives you identity-based access instead of relying on changing IP addresses. Configure the application so unauthenticated visitors are redirected to sign-in, then grant access only to the appropriate users or groups.
App Service is another reasonable choice, particularly if you want a straightforward built-in authentication configuration. You can place Entra ID authentication in front of the site and control access with group membership, MFA, and Conditional Access policies. It may cost more than Blob Storage, but it is a cleaner fit when the site must have protected browser access.
The simplest option may be to host or embed the dashboard directly in SharePoint instead of exposing a separate public Blob Storage website. You can still use Power Automate to update the underlying content, and SharePoint authentication automatically limits access to your organization’s users. Check whether the dashboard’s scripts and interactive features work correctly when embedded, since iframe and content-security restrictions can matter.
Private Link and Front Door are not substitutes for end-user authentication. Private Link is mainly for private network connectivity, which can make remote access more complicated unless you also provide a managed private-access solution. For this scenario, Entra ID authentication with MFA and Conditional Access is usually more appropriate. If you already license it, Entra Private Access could provide another way to publish the application securely without deploying a traditional VPN to every laptop.
Static Web Apps can also handle Entra authentication, so App Service isn’t the only viable choice. The important part is putting an identity-aware authentication layer in front of the content rather than trying to secure a public storage URL.