A partner nonprofit needs limited access to a city planning app but should not receive a full municipal employee account. Which Azure identity approach fits that use case?
Select an answer to reveal the explanation.
Short Explanation
Partners who need a slice of access—not a city badge for life—are a textbook external-identity scenario. Guest access keeps them outside the full employee roster while still letting them sign in. Full Owner for every volunteer is the opposite of limited access.
Full Explanation
External identities are designed for partners, vendors, and other outside organizations that need controlled access without full employee accounts. Assigning broad Owner rights, sharing global admin credentials, or removing authentication entirely contradict least-privilege municipal practice. Fundamentals items emphasize recognizing when guest/external identity is the right pattern.