Extend the platform2 / 5
A developer needs to manage sensitive input and output parameters in a Power Automate cloud flow. The flow processes credit card numbers that should not appear in run history. What should the developer configure?
CorrectIncorrect
Alex
Microsoft docs confirm that Secure Inputs and Secure Outputs settings on Power Automate actions mask sensitive values in run history and audit logs. This is the correct approach for credit card numbers and sensitive data. Storing in an environment variable (the option “Store the credit card in an environment variable marked as…”) protects the value at rest but does not prevent exposure in run history. A Compose action (the option “Use a Compose action to mask the data before processing”) provides no built-in masking capability. Disabling run history storage (the option “Set the flow to run without storing run history”) would hide all data, not just sensitive fields, and removes valuable debugging capability.
Sourcelearn.microsoft.com
Follow-up answers are available in the app. Create a free account — no credit card required.
Question 2 of 5
Create a free account