SC-300 · Question #241
You have an Azure AD tenant and a .NET web app named App1. You need to register App1 for Azure AD authentication. What should you configure for App1?
The correct answer is D. the redirect URI. Explanation When registering a .NET web application with Azure AD, you must configure a redirect URI - this is the URL where Azure AD sends the authentication response (including tokens) after a user successfully signs in, making it essential for the OAuth 2.0/OpenID Connect…
Question
You have an Azure AD tenant and a .NET web app named App1. You need to register App1 for Azure AD authentication. What should you configure for App1?
Options
- Athe executable name
- Bthe bundle ID
- Cthe package name
- Dthe redirect URI
How the community answered
(42 responses)- B2% (1)
- C5% (2)
- D93% (39)
Explanation
Explanation
When registering a .NET web application with Azure AD, you must configure a redirect URI - this is the URL where Azure AD sends the authentication response (including tokens) after a user successfully signs in, making it essential for the OAuth 2.0/OpenID Connect flow to work correctly.
Why the distractors are wrong:
- A. Executable name - This is relevant for desktop/native applications on Windows, not web apps registered in Azure AD.
- B. Bundle ID - This is an Apple iOS/macOS concept used to identify mobile applications, irrelevant to Azure AD web app registration.
- C. Package name - This is an Android-specific identifier used for mobile apps, not applicable to .NET web applications.
Memory Tip
Think of the redirect URI as a "return address" on a letter - after Azure AD authenticates the user, it needs to know where to send the token back to. The type of identifier needed always matches the platform: URI for web apps, bundle ID for iOS, package name for Android. Since App1 is a .NET web app, a URI (web address) is the logical choice.
Topics
Community Discussion
No community discussion yet for this question.