-
Notifications
You must be signed in to change notification settings - Fork 217
Web App Samples
Jean-Marc Prieur edited this page Nov 16, 2020
·
6 revisions
To see Microsoft Identity Web in action, or to learn how to sign-in users with a web app and call a protected web API, use this incremental tutorial on ASP .NET Core web apps which signs-in users (including in your org, many orgs, orgs + personal accounts, sovereign clouds) and calls web APIs (including Microsoft Graph), while leveraging Microsoft Identity Web. See the incremental tutorial.
- Web app which signs in users
- Web app which signs in users and calls Graph
- Web app which signs in users and calls multiple web APIs
- See the incremental tutorial for even more samples, including B2C.
-
Azure Storage sample. See in particular the controller, as well as the TokenAcquisitionTokenCredential class which adapts a
ITokenAcquisition
to an Azure SDKTokenCredential
. - Microsoft Graph Web hooks sample (for ASP.NET Core)
If you are interested in web APIs, see Web-API-Samples
- Home
- Why use Microsoft Identity Web?
- Web apps
- Web APIs
- Using certificates
- Minimal support for .NET FW Classic
- Logging
- Azure AD B2C limitations
- Samples
- Web apps
- Web app samples
- Web app template
- Call an API from a web app
- Managing incremental consent and conditional access
- Web app troubleshooting
- Deploy to App Services Linux containers or with proxies
- SameSite cookies
- Hybrid SPA
- Web APIs
- Web API samples
- Web API template
- Call an API from a web API
- Token Decryption
- Web API troubleshooting
- web API protected by ACLs instead of app roles
- gRPC apps
- Azure Functions
- Long running processes in web APIs
- Authorization policies
- Generic API
- Customization
- Logging
- Calling graph with specific scopes/tenant
- Multiple Authentication Schemes
- Utility classes
- Setting FIC+MSI
- Mixing web app and web API
- Deploying to Azure App Services
- Azure AD B2C issuer claim support
- Performance
- specify Microsoft Graph scopes and app-permissions
- Integrate with Azure App Services authentication
- Ajax calls and incremental consent and conditional access
- Back channel proxys
- Client capabilities