As the architect of MDFT Pro, a well-known training agency, you design several Azure logic apps that have HTTP triggers. The logic apps provide access to an on-premises web service.
MDFT Pro establishes a partnership with another company. The partner does not have an existing Azure Active Directory (Azure AD) tenant and uses third-party OAuth 2.0 identity management to authenticate its users.
Developers at the partner company plan to use a subset of the logic apps to build applications that will integrate with the on-premises web service of MDFT Pro.
You need to design a solution to provide the partner developers with access to the logic apps. The solution must meet the following requirements:
- Requests to the logic apps from the developers must be limited to lower rates than the requests from the users at MDFT Pro.
- The developers must be able to rely on their existing OAuth 2.0 provider to gain access to the logic apps.
- The solution must NOT require changes to the logic apps.
- The solution must NOT use Azure AD guest accounts.
What should you include in the solution?
Azure API Management is correct. Azure API Management can enforce rate limits per consumer, validate JWT tokens from the existing OAuth 2.0 provider, and sit in front of the logic apps without requiring changes to them.
Azure Front Door is incorrect. Azure Front Door is a global routing and WAF service that cannot enforce per-developer rate limits, integrate with the OAuth 2.0 provider, or proxy to logic apps without changes.
Azure AD Application Proxy is incorrect. Azure AD Application Proxy is designed for on-premises application access via Azure AD accounts, not for third-party OAuth providers or external partner developer access scenarios.
Azure AD business-to-business (B2B) is incorrect. Azure AD B2B requires guest accounts in the tenant, which the solution explicitly prohibits.