-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Interactive Auto rendering for holistic project #266
Comments
Alternatively - just a feature request that shows this sample with Integrated Auth (either Entra pre-auth or MSAL via internal app checking) would also be great! We've done this with MSAL but were unable to get "Easy Authentication" to forward the token for OBO API-to-API flows on the back-end - maybe there's a way... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is for a: (mark with an
x
)Given that this project has been migrated to .NET 8, it would be nice to have this sample take advantage of the new "preload" Interactive render features in Blazor. Any production branching that is being created will likely include mandatory authentication (as I've done) which forces the dreaded double-load of the WASM package without a first render (even with cached packages, still a pretty suboptimal user experience).
I understand MSAL is quite finicky with the new modality, just placing this here as this is a great repo that demos a lot of features that are hard to find elsewhere (generic azure openai samples in general are dime-a-dozen).
Much of what I've been able to learn about Doc Intelligence options, Bicep authoring, and AI Search has come from this sample, so thanks!
The text was updated successfully, but these errors were encountered: