Work with Approvals and Adaptive Cards

Reference documentation tells you what the platform exposes; this lesson focuses on how to reason while using it. The example is intentionally small enough to inspect completely, but the decisions are the same ones that appear in larger Microsoft Power Platform systems. In this lesson's Approvals and Adaptive Cards example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Automate exercise changes the conditions.

In this lesson

• Place Approvals and Adaptive Cards in the context of the Power Automate module rather than treating it as an isolated feature.
• Build a mental model for what happens before, during, and after the operation.
• Work through a reproducible example connected to the scenario: automate an internal request-and-approval process with governed data.
• Inspect the result and distinguish evidence from assumption.
• Recognize failure modes, misleading shortcuts, and production constraints.
• Leave with a verification checklist and a practical exercise rather than a memorized snippet.

Interactions with neighboring concepts

For a Power Platform maker/developer, Approvals and Adaptive Cards becomes useful when it changes a decision you can verify. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. The specific test here is about Approvals and Adaptive Cards: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

The practical question behind work with approvals and adaptive cards is not simply whether the feature exists, but what behavior it gives you control over. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—automate an internal request-and-approval process with governed data—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by Approvals and Adaptive Cards; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. In this lesson's Approvals and Adaptive Cards example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Automate exercise changes the conditions.

Failure modes that reveal misunderstanding

Before adding more syntax, make the state of the system observable. That habit matters especially when working with Approvals and Adaptive Cards. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. In this lesson's Approvals and Adaptive Cards example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Automate exercise changes the conditions. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of Approvals and Adaptive Cards over another. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—automate an internal request-and-approval process with governed data—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by Approvals and Adaptive Cards; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. Keep this point tied to Approvals and Adaptive Cards. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Automate lesson are specific to this mechanism. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

Questions to answer about Approvals and Adaptive Cards

1. What is the smallest input or state that makes Approvals and Adaptive Cards observable?
2. What does success look like, and how can you prove it without relying on a vague UI message?
3. Which configuration, permissions, types, versions or environment details can change the result?
4. Which failure is most likely for a beginner, and what evidence distinguishes it from a different failure?
5. What should remain true after the example is repeated, automated or moved to another environment?

Choosing between common alternatives

In the Power Automate part of this learning path, Approvals and Adaptive Cards is deliberately introduced now because later lessons depend on the boundary it establishes. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. The specific test here is about Approvals and Adaptive Cards: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

A production system rarely fails at the exact line shown in a beginner example, so this section connects Approvals and Adaptive Cards to the surrounding runtime and operational context. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—automate an internal request-and-approval process with governed data—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by Approvals and Adaptive Cards; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. Keep this point tied to Approvals and Adaptive Cards. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Automate lesson are specific to this mechanism. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

Testing the behavior

For a Power Platform maker/developer, Approvals and Adaptive Cards becomes useful when it changes a decision you can verify. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. In this lesson's Approvals and Adaptive Cards example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Automate exercise changes the conditions. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

The practical question behind work with approvals and adaptive cards is not simply whether the feature exists, but what behavior it gives you control over. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—automate an internal request-and-approval process with governed data—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by Approvals and Adaptive Cards; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. Keep this point tied to Approvals and Adaptive Cards. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Automate lesson are specific to this mechanism. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

Evidence table

What you inspect	What it tells you	What it does not prove
Source/configuration for Approvals and Adaptive Cards	What you asked the platform/runtime to do	That the request actually succeeded
Build/validation output	Whether static checks accepted the artifact	That production data and permissions behave correctly
Runtime/result output	What happened for this input	That every edge case is safe
Logs/diagnostics	Where the system spent time or failed	The root cause without interpretation
Repeat test	Whether behavior is reproducible	That the design is optimal

Maintainability and readability

In Maintainability and readability, look at Approvals and Adaptive Cards through the constraint that matters in this part of the lesson: make the relevant state visible before you change it, then compare the observed result with the contract you expected. In Microsoft Power Platform, this prevents a local-looking edit from hiding an environment, data, permission, lifecycle or runtime assumption. Record the evidence from this step because the next decision in the Power Automate module should be based on what you measured rather than on a repeated rule of thumb.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of Approvals and Adaptive Cards over another. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—automate an internal request-and-approval process with governed data—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by Approvals and Adaptive Cards; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. For Approvals and Adaptive Cards, apply this check in the context of the Power Automate workflow before carrying the assumption into later Microsoft Power Platform work.

Performance or operational implications

In the Power Automate part of this learning path, Approvals and Adaptive Cards is deliberately introduced now because later lessons depend on the boundary it establishes. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. Keep this point tied to Approvals and Adaptive Cards. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Automate lesson are specific to this mechanism.

A production system rarely fails at the exact line shown in a beginner example, so this section connects Approvals and Adaptive Cards to the surrounding runtime and operational context. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—automate an internal request-and-approval process with governed data—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by Approvals and Adaptive Cards; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. In this lesson's Approvals and Adaptive Cards example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Automate exercise changes the conditions. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

Worked example: Approvals and Adaptive Cards

The following powerfx example is written specifically for this lesson. Read the requirement first, then predict the important result before running or reproducing it.

If(
    IsBlank(txtRequestTitle.Text),
    Notify("Enter a request title", NotificationType.Error),
    Patch(
        Requests,
        Defaults(Requests),
        { Title: txtRequestTitle.Text, Status: "Draft" }
    )
)

Expected observation

A validation notification or a new Draft request record.

Read the example deliberately

• Line/construct 1: If( — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 2: IsBlank(txtRequestTitle.Text), — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 3: Notify("Enter a request title", NotificationType.Error), — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 4: Patch( — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 5: Requests, — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 6: Defaults(Requests), — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 7: { Title: txtRequestTitle.Text, Status: "Draft" } — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 8: ) — identify what state or contract this introduces, then trace where that state is consumed.
• Line/construct 9: ) — identify what state or contract this introduces, then trace where that state is consumed.

Do not stop at “it ran.” Change one meaningful value related to Approvals and Adaptive Cards, predict the new result, run/reproduce the example again, and explain why the output changed. That mutation test is a stronger check of understanding than copying the original result.

Practice variation

For a Power Platform maker/developer, Approvals and Adaptive Cards becomes useful when it changes a decision you can verify. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. Keep this point tied to Approvals and Adaptive Cards. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Automate lesson are specific to this mechanism. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

The practical question behind work with approvals and adaptive cards is not simply whether the feature exists, but what behavior it gives you control over. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—automate an internal request-and-approval process with governed data—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by Approvals and Adaptive Cards; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. For Approvals and Adaptive Cards, apply this check in the context of the Power Automate workflow before carrying the assumption into later Microsoft Power Platform work.

Review questions

Before adding more syntax, make the state of the system observable. That habit matters especially when working with Approvals and Adaptive Cards. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. Keep this point tied to Approvals and Adaptive Cards. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Automate lesson are specific to this mechanism. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of Approvals and Adaptive Cards over another. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—automate an internal request-and-approval process with governed data—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by Approvals and Adaptive Cards; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. In this lesson's Approvals and Adaptive Cards example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Automate exercise changes the conditions. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

Failure-mode matrix

Symptom	Likely category	First evidence to collect
The Approvals and Adaptive Cards behavior never occurs	configuration / control flow	verify the relevant code/configuration is actually reached
Build or validation fails	syntax / type / unsupported option	read the first meaningful diagnostic, not the last cascade message
Works locally but not elsewhere	environment / version / permission	compare runtime versions, identity, configuration and data
Result is valid but wrong	assumption / data shape / business rule	inspect intermediate values and boundary conditions
Intermittent behavior	concurrency / timing / external dependency	add timestamps, correlation IDs or deterministic reproduction

Where to go next

In the Power Automate part of this learning path, Approvals and Adaptive Cards is deliberately introduced now because later lessons depend on the boundary it establishes. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. In this lesson's Approvals and Adaptive Cards example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Automate exercise changes the conditions. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

Now apply Approvals and Adaptive Cards to the current Where to go next concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Microsoft Power Platform runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

The idea behind Approvals and Adaptive Cards

For this part of Work with Approvals and Adaptive Cards, move beyond the earlier mental model and ask how the behavior survives repetition. Run or reproduce the step twice, change the ordering or boundary case where safe, and verify that the same invariant still holds. A reliable Power Automate workflow is one that produces evidence you can compare, not one that succeeds only when the exact tutorial sequence is copied.

The practical question behind work with approvals and adaptive cards is not simply whether the feature exists, but what behavior it gives you control over. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—automate an internal request-and-approval process with governed data—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by Approvals and Adaptive Cards; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. The specific test here is about Approvals and Adaptive Cards: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

Mental model before syntax

Before adding more syntax, make the state of the system observable. That habit matters especially when working with Approvals and Adaptive Cards. One useful review technique is to remove or alter a single element and predict what should happen. If the prediction is wrong, the gap is conceptual rather than syntactic. The exercises use that technique because it gives stronger evidence of understanding than simply retyping a finished example. The specific test here is about Approvals and Adaptive Cards: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

Now apply Approvals and Adaptive Cards to the current Mental model before syntax concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Microsoft Power Platform runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

Terminology and boundaries

Now apply Approvals and Adaptive Cards to the current Terminology and boundaries concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Microsoft Power Platform runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

For the Terminology and boundaries part of Work with Approvals and Adaptive Cards, use a separate verification pass rather than repeating the earlier explanation. Focus on Approvals and Adaptive Cards under one changed condition and write down the before/after evidence. This is verification pass 2 for Microsoft Power Platform lesson 32: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Power Automate workflow.

How the mechanism behaves step by step

This section needs a different question from the earlier explanation: what would make Approvals and Adaptive Cards fail specifically while working through How the mechanism behaves step by step? Choose one realistic boundary, reproduce it deliberately, and inspect the first useful diagnostic or intermediate value. The aim in Work with Approvals and Adaptive Cards is to recognize the mechanism under changed conditions, not to repeat the same successful path with different wording.

Now apply Approvals and Adaptive Cards to the current How the mechanism behaves step by step concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Microsoft Power Platform runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

Syntax or configuration anatomy

In Syntax or configuration anatomy, look at Approvals and Adaptive Cards through the constraint that matters in this part of the lesson: make the relevant state visible before you change it, then compare the observed result with the contract you expected. In Microsoft Power Platform, this prevents a local-looking edit from hiding an environment, data, permission, lifecycle or runtime assumption. Record the evidence from this step because the next decision in the Power Automate module should be based on what you measured rather than on a repeated rule of thumb.

Now apply Approvals and Adaptive Cards to the current Syntax or configuration anatomy concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Microsoft Power Platform runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

Worked example built from a real requirement

In Worked example built from a real requirement, look at Approvals and Adaptive Cards through the constraint that matters in this part of the lesson: make the relevant state visible before you change it, then compare the observed result with the contract you expected. In Microsoft Power Platform, this prevents a local-looking edit from hiding an environment, data, permission, lifecycle or runtime assumption. Record the evidence from this step because the next decision in the Power Automate module should be based on what you measured rather than on a repeated rule of thumb.

For the Worked example built from a real requirement part of Work with Approvals and Adaptive Cards, use a separate verification pass rather than repeating the earlier explanation. Focus on Approvals and Adaptive Cards under one changed condition and write down the before/after evidence. This is verification pass 2 for Microsoft Power Platform lesson 32: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Power Automate workflow.

Trace the example line by line

For the Trace the example line by line part of Work with Approvals and Adaptive Cards, use a separate verification pass rather than repeating the earlier explanation. Focus on Approvals and Adaptive Cards under one changed condition and write down the before/after evidence. This is verification pass 2 for Microsoft Power Platform lesson 32: the useful outcome is a concrete observation—output, state, diagnostic, generated artifact, query result or test result—that another learner can reproduce in the Power Automate workflow.

This section needs a different question from the earlier explanation: what would make Approvals and Adaptive Cards fail specifically while working through Trace the example line by line? Choose one realistic boundary, reproduce it deliberately, and inspect the first useful diagnostic or intermediate value. The aim in Work with Approvals and Adaptive Cards is to recognize the mechanism under changed conditions, not to repeat the same successful path with different wording.

Variants you will meet in real code

Now apply Approvals and Adaptive Cards to the current Variants you will meet in real code concern. Start from the smallest state that demonstrates the behavior, vary one input or configuration choice, and explain the result in terms of the Microsoft Power Platform runtime or platform. If two outcomes look similar in the UI, use logs, return values, generated artifacts, query results, tests or another concrete signal to distinguish them.

There are usually several ways to accomplish the same visible result. The important skill is knowing which guarantees differ when you choose one form of Approvals and Adaptive Cards over another. The learner should be able to describe the inputs, the operation, and the result in plain language. In the running scenario—automate an internal request-and-approval process with governed data—the input might be a value, request, record, event, configuration setting, or user action. The operation is the part controlled by Approvals and Adaptive Cards; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. The specific test here is about Approvals and Adaptive Cards: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

A production-oriented walkthrough for Approvals and Adaptive Cards

1. Establish the Approvals and Adaptive Cards behavior

Establish this step in the context of automate an internal request-and-approval process with governed data. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to a developer environment and maker portal. In this lesson's Approvals and Adaptive Cards example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Automate exercise changes the conditions.

2. Inspect the Approvals and Adaptive Cards behavior

3. Implement the Approvals and Adaptive Cards behavior

A useful variation is to introduce one boundary case that is plausible for Approvals and Adaptive Cards: an empty value, a missing permission, an unexpected type, a repeated operation, an unavailable dependency, or a larger-than-normal input. The exact case depends on the technology, but the reasoning is the same—state the invariant you expect to remain true, then verify it explicitly. Keep this point tied to Approvals and Adaptive Cards. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Automate lesson are specific to this mechanism.

4. Exercise the Approvals and Adaptive Cards behavior

5. Challenge the Approvals and Adaptive Cards behavior

A useful variation is to introduce one boundary case that is plausible for Approvals and Adaptive Cards: an empty value, a missing permission, an unexpected type, a repeated operation, an unavailable dependency, or a larger-than-normal input. The exact case depends on the technology, but the reasoning is the same—state the invariant you expect to remain true, then verify it explicitly. For Approvals and Adaptive Cards, apply this check in the context of the Power Automate workflow before carrying the assumption into later Microsoft Power Platform work. In Microsoft Power Platform lesson 32 — Work with Approvals and Adaptive Cards, use that observation as the checkpoint for this exact Power Automate topic rather than generalizing it beyond the evidence.

6. Verify the Approvals and Adaptive Cards behavior

7. Harden the Approvals and Adaptive Cards behavior

Harden this step in the context of automate an internal request-and-approval process with governed data. Keep the change small enough that you can state the expected result before executing it. Capture the relevant input, configuration or code, then record the observable result. If the result differs from the prediction, do not add more changes yet; narrow the mismatch using diagnostics appropriate to a developer environment and maker portal. The specific test here is about Approvals and Adaptive Cards: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

In A production-oriented walkthrough for Approvals and Adaptive Cards, look at Approvals and Adaptive Cards through the constraint that matters in this part of the lesson: make the relevant state visible before you change it, then compare the observed result with the contract you expected. In Microsoft Power Platform, this prevents a local-looking edit from hiding an environment, data, permission, lifecycle or runtime assumption. Record the evidence from this step because the next decision in the Power Automate module should be based on what you measured rather than on a repeated rule of thumb.

8. Document the Approvals and Adaptive Cards behavior

Missteps to catch before they become habits

Treating Approvals and Adaptive Cards as syntax instead of behavior

If you can reproduce the syntax but cannot predict the state after it runs, the lesson is not finished. Rewrite the example in your own words and name the input, operation and observable result.

Copying a configuration from a different version

Microsoft Power Platform tooling evolves. Compare the documentation version, runtime/tool version and project settings before assuming that a screenshot or command from another environment applies unchanged.

Verifying only the happy path

A successful first run proves one path. Add at least one negative or boundary case relevant to Approvals and Adaptive Cards. The failure should be intentional and the diagnostic should make sense.

Hiding the important state behind too much abstraction

Abstraction is useful after the behavior is understood. During the first implementation of Approvals and Adaptive Cards, keep the decisive state and control flow visible enough to debug.

When Approvals and Adaptive Cards does not behave as expected

Use this order when Approvals and Adaptive Cards does not behave as expected:

1. Reproduce the smallest failing case.
2. Confirm the actual version/toolchain/environment.
3. Capture the first meaningful diagnostic or unexpected value.
4. Verify identity, permissions and configuration if the operation crosses a service boundary.
5. Inspect intermediate state rather than only the final UI.
6. Change one variable and rerun.
7. Compare the corrected behavior with a negative case.
8. Record the final cause so the same failure is faster to diagnose next time.

Put Approvals and Adaptive Cards under pressure

Extend the worked scenario so that Approvals and Adaptive Cards must handle one additional real constraint. Choose one: a second data shape, a failed dependency, an invalid input, a permission difference, a repeat operation, or a larger workload. Before implementing the change, write down the behavior you expect and the evidence that will prove it.

Your result is complete when another learner can reproduce the change from your notes, observe the expected behavior, and intentionally trigger at least one documented failure without damaging their environment. In this lesson's Approvals and Adaptive Cards example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Automate exercise changes the conditions.

Can you explain and verify Approvals and Adaptive Cards?

• Can you define Approvals and Adaptive Cards without using the exact wording of an API/reference page?
• Can you identify the boundary where Approvals and Adaptive Cards begins and where another concept takes over?
• Can you predict the result of the worked example before running it?
• Can you explain one failure from evidence rather than guessing?
• Can you name one production constraint that the beginner example intentionally simplifies?
• Can you repeat the example from a clean state?

The durable ideas from Approvals and Adaptive Cards

• Approvals and Adaptive Cards is useful because it controls observable behavior, not because it adds another piece of syntax to memorize.
• Verification belongs in the workflow: build/check, run/reproduce, inspect, challenge, and repeat.
• The Power Automate module uses this lesson as a foundation for the next decisions in the Microsoft Power Platform learning path.
• Official documentation is the source of truth for version-specific contracts; tutorials should teach you how to read and apply those contracts.

Documentation to keep beside this lesson

The following primary documentation was used as a factual reference map for this lesson. ScrutnLearn's explanation is original synthesis rather than copied documentation prose.

• Power Automate documentation
• Power Apps documentation
• Power BI documentation
• Power Pages documentation
• Power Platform developer documentation