Configure Custom Connector Authentication for Test/Prod
You build a canvas app that connects to a custom API using a custom connector. The API allows the app to connect to a test or production instance of the service. Users must provide a unique login and password combination that is specific to either test or production. You need to configure the authentication settings in the connector. What should you configure?
Community Votes
67% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests knowledge of the apiProperties.json structure; the trap is choosing generic connectionParameters instead of the specific connectionParameterSets required for environment switching.
Learn how to configure a Power Apps custom connector to support distinct test and production environments using connectionParameterSets in apiProperties.json. This page clarifies the correct JSON property for multi-environment authentication.
Learners often select 'connectionParameters' because it seems like the logical place for login/password settings, missing that 'connectionParameterSets' is the mechanism for defining multiple distinct sets of parameters for different environments.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The question requires supporting two distinct environments (test and production) with unique credentials within a single custom connector. In theapiProperties.json file for a custom connector, the connectionParameterSets object is specifically designed to define multiple sets of connection parameters. Each set can have a unique name (e.g., "Test" and "Production") and its own set of required parameters (like username and password). This allows the user to select the appropriate environment when connecting the app.Why the Other Options Are Wrong
Option C,connectionParameters, defines the individual parameters themselves (like the schema for a username or password field), but it does not provide the structure to group them into distinct environment-specific sets. Option B, apiDefinition, refers to the OpenAPI specification (Swagger) that defines the API's operations, endpoints, and schemas, not the authentication configuration logic.Community Comment Notes
Community consensus strongly favors option A. As Paliukova noted, "ConnectionParameterSets Allows you to configure multiple connection parameters within a single connector." Another commenter, sugaSri, emphasized that this feature is "specifically designed to manage multiple sets of connection parameters, making it easier to switch between different environments." While one user voted for C, the majority correctly identified that the sets are what enable the environment choice.Official Reference
Exam Strategy
When configuring custom connectors, always check if the requirement involves multiple environments or authentication methods. If so, look for 'connectionParameterSets' in apiProperties.json rather than just 'connectionParameters'. The key is distinguishing between defining a parameter type versus grouping parameters into named sets.
Frequently Asked Questions
Why not use connectionParameters for test and prod?
connectionParameters defines the individual fields (like username/password types). connectionParameterSets groups these fields into named sets (e.g., 'Test', 'Prod') so users can choose which environment to connect to.
What is the role of apiDefinition in custom connectors?
apiDefinition contains the OpenAPI/Swagger spec describing the API's endpoints and operations. It does not handle the connection parameter grouping for authentication environments.