Create and Configure a Power Pages Site

The fastest way to misunderstand and Configure a Power Pages Site is to memorize its surface syntax without learning the boundary it controls. We will use automate an internal request-and-approval process with governed data as a concrete thread, so each choice has an observable consequence rather than becoming a list of disconnected facts.

In this lesson

• Place and Configure a Power Pages Site in the context of the Power Pages 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.

Before touching the installer

For a Power Platform maker/developer, and Configure a Power Pages Site becomes useful when it changes a decision you can verify. 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 and Configure a Power Pages Site; the result is the state you can inspect afterward. Keeping those three pieces explicit prevents the lesson from collapsing into memorized commands. For and Configure a Power Pages Site, apply this check in the context of the Power Pages workflow before carrying the assumption into later Microsoft Power Platform work. In Microsoft Power Platform lesson 60 — Create and Configure a Power Pages Site, use that observation as the checkpoint for this exact Power Pages topic rather than generalizing it beyond the evidence.

The practical question behind create and configure a power pages site is not simply whether the feature exists, but what behavior it gives you control over. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. In this lesson's and Configure a Power Pages Site example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Pages exercise changes the conditions. In Microsoft Power Platform lesson 60 — Create and Configure a Power Pages Site, use that observation as the checkpoint for this exact Power Pages topic rather than generalizing it beyond the evidence.

Supported paths and practical constraints

Before adding more syntax, make the state of the system observable. That habit matters especially when working with and Configure a Power Pages Site. 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 and Configure a Power Pages Site; 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 and Configure a Power Pages Site: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above. In Microsoft Power Platform lesson 60 — Create and Configure a Power Pages Site, use that observation as the checkpoint for this exact Power Pages 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 and Configure a Power Pages Site over another. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. In this lesson's and Configure a Power Pages Site example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Pages exercise changes the conditions. In Microsoft Power Platform lesson 60 — Create and Configure a Power Pages Site, use that observation as the checkpoint for this exact Power Pages topic rather than generalizing it beyond the evidence.

Questions to answer about and Configure a Power Pages Site

1. What is the smallest input or state that makes and Configure a Power Pages Site 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?

What will be installed and where it lives

In the Power Pages part of this learning path, and Configure a Power Pages Site is deliberately introduced now because later lessons depend on the boundary it establishes. 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 and Configure a Power Pages Site; 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 and Configure a Power Pages Site. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Pages lesson are specific to this mechanism. In Microsoft Power Platform lesson 60 — Create and Configure a Power Pages Site, use that observation as the checkpoint for this exact Power Pages 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 and Configure a Power Pages Site to the surrounding runtime and operational context. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. Keep this point tied to and Configure a Power Pages Site. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Pages lesson are specific to this mechanism.

Step-by-step setup for and Configure a Power Pages Site

For a Power Platform maker/developer, and Configure a Power Pages Site becomes useful when it changes a decision you can verify. 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 and Configure a Power Pages Site; 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 and Configure a Power Pages Site. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Pages lesson are specific to this mechanism.

The practical question behind create and configure a power pages site is not simply whether the feature exists, but what behavior it gives you control over. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. For and Configure a Power Pages Site, apply this check in the context of the Power Pages workflow before carrying the assumption into later Microsoft Power Platform work. In Microsoft Power Platform lesson 60 — Create and Configure a Power Pages Site, use that observation as the checkpoint for this exact Power Pages 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 and Configure a Power Pages Site	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

Verification: prove the setup actually works

Before adding more syntax, make the state of the system observable. That habit matters especially when working with and Configure a Power Pages Site. 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 and Configure a Power Pages Site; 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 and Configure a Power Pages Site example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Pages exercise changes the conditions. In Microsoft Power Platform lesson 60 — Create and Configure a Power Pages Site, use that observation as the checkpoint for this exact Power Pages 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 and Configure a Power Pages Site over another. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. The specific test here is about and Configure a Power Pages Site: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

Understand the files, processes and settings created

For this part of Create and Configure a Power Pages Site, 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 Pages workflow is one that produces evidence you can compare, not one that succeeds only when the exact tutorial sequence is copied.

A production system rarely fails at the exact line shown in a beginner example, so this section connects and Configure a Power Pages Site to the surrounding runtime and operational context. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. The specific test here is about and Configure a Power Pages Site: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above. In Microsoft Power Platform lesson 60 — Create and Configure a Power Pages Site, use that observation as the checkpoint for this exact Power Pages topic rather than generalizing it beyond the evidence.

Worked example: and Configure a Power Pages Site

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 and Configure a Power Pages Site, 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.

Configuration choices worth making now

Now apply and Configure a Power Pages Site to the current Configuration choices worth making now 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 Configuration choices worth making now part of Create and Configure a Power Pages Site, use a separate verification pass rather than repeating the earlier explanation. Focus on and Configure a Power Pages Site under one changed condition and write down the before/after evidence. This is verification pass 2 for Microsoft Power Platform lesson 60: 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 Pages workflow.

A first smoke test

Before adding more syntax, make the state of the system observable. That habit matters especially when working with and Configure a Power Pages Site. 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 and Configure a Power Pages Site; 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 and Configure a Power Pages Site. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Pages lesson are specific to this mechanism.

For the A first smoke test part of Create and Configure a Power Pages Site, use a separate verification pass rather than repeating the earlier explanation. Focus on and Configure a Power Pages Site under one changed condition and write down the before/after evidence. This is verification pass 2 for Microsoft Power Platform lesson 60: 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 Pages workflow.

Failure-mode matrix

Symptom	Likely category	First evidence to collect
The and Configure a Power Pages Site 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

Typical setup failures and their real causes

In the Power Pages part of this learning path, and Configure a Power Pages Site is deliberately introduced now because later lessons depend on the boundary it establishes. 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 and Configure a Power Pages Site; 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 and Configure a Power Pages Site: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

A production system rarely fails at the exact line shown in a beginner example, so this section connects and Configure a Power Pages Site to the surrounding runtime and operational context. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. For and Configure a Power Pages Site, apply this check in the context of the Power Pages workflow before carrying the assumption into later Microsoft Power Platform work.

Repair strategy without reinstalling everything

For a Power Platform maker/developer, and Configure a Power Pages Site becomes useful when it changes a decision you can verify. 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 and Configure a Power Pages Site; 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 and Configure a Power Pages Site: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

For the Repair strategy without reinstalling everything part of Create and Configure a Power Pages Site, use a separate verification pass rather than repeating the earlier explanation. Focus on and Configure a Power Pages Site under one changed condition and write down the before/after evidence. This is verification pass 3 for Microsoft Power Platform lesson 60: 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 Pages workflow.

Keeping multiple versions/environments under control

Now apply and Configure a Power Pages Site to the current Keeping multiple versions/environments under control 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 and Configure a Power Pages Site over another. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. For and Configure a Power Pages Site, apply this check in the context of the Power Pages workflow before carrying the assumption into later Microsoft Power Platform work. In Microsoft Power Platform lesson 60 — Create and Configure a Power Pages Site, use that observation as the checkpoint for this exact Power Pages topic rather than generalizing it beyond the evidence.

Security and permissions considerations

Now apply and Configure a Power Pages Site to the current Security and permissions considerations 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.

This section needs a different question from the earlier explanation: what would make and Configure a Power Pages Site fail specifically while working through Security and permissions considerations? Choose one realistic boundary, reproduce it deliberately, and inspect the first useful diagnostic or intermediate value. The aim in Create and Configure a Power Pages Site is to recognize the mechanism under changed conditions, not to repeat the same successful path with different wording.

Upgrade and cleanup strategy

For a Power Platform maker/developer, and Configure a Power Pages Site becomes useful when it changes a decision you can verify. 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 and Configure a Power Pages Site; 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 and Configure a Power Pages Site example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Pages exercise changes the conditions.

The practical question behind create and configure a power pages site is not simply whether the feature exists, but what behavior it gives you control over. Documentation often presents the API or syntax first because reference pages are written for lookup. A tutorial has a different job. Here the explanation begins with intent, then shows the smallest concrete implementation, then adds constraints. That order lets you understand why a setting or line exists before you are asked to remember its spelling. Keep this point tied to and Configure a Power Pages Site. The same general engineering habit appears elsewhere, but the evidence and failure signals in this Power Pages lesson are specific to this mechanism.

Checkpoint before the next lesson

In Checkpoint before the next lesson, look at and Configure a Power Pages Site 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 Pages module should be based on what you measured rather than on a repeated rule of thumb.

Now apply and Configure a Power Pages Site to the current Checkpoint before the next lesson 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.

A production-oriented walkthrough for and Configure a Power Pages Site

1. Establish the and Configure a Power Pages Site behavior

2. Inspect the and Configure a Power Pages Site behavior

3. Implement the and Configure a Power Pages Site behavior

A useful variation is to introduce one boundary case that is plausible for and Configure a Power Pages Site: 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. The specific test here is about and Configure a Power Pages Site: change one relevant input, configuration value or boundary and make sure the result still matches the contract described above.

4. Exercise the and Configure a Power Pages Site behavior

Exercise 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. For and Configure a Power Pages Site, apply this check in the context of the Power Pages workflow before carrying the assumption into later Microsoft Power Platform work.

5. Challenge the and Configure a Power Pages Site behavior

Challenge 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 and Configure a Power Pages Site example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Pages exercise changes the conditions.

A useful variation is to introduce one boundary case that is plausible for and Configure a Power Pages Site: 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 and Configure a Power Pages Site, apply this check in the context of the Power Pages workflow before carrying the assumption into later Microsoft Power Platform work.

6. Verify the and Configure a Power Pages Site behavior

7. Harden the and Configure a Power Pages Site behavior

A useful variation is to introduce one boundary case that is plausible for and Configure a Power Pages Site: 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. In this lesson's and Configure a Power Pages Site example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Pages exercise changes the conditions.

8. Document the and Configure a Power Pages Site behavior

Tempting shortcuts that weaken and Configure a Power Pages Site

Treating and Configure a Power Pages Site 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 and Configure a Power Pages Site. 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 and Configure a Power Pages Site, keep the decisive state and control flow visible enough to debug.

Recovering from common and Configure a Power Pages Site failures

Use this order when and Configure a Power Pages Site 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.

Challenge the worked example

Extend the worked scenario so that and Configure a Power Pages Site 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 and Configure a Power Pages Site example, record the evidence you observed rather than treating the rule as a slogan; that note becomes useful when the next Power Pages exercise changes the conditions.

Evidence that you understand and Configure a Power Pages Site

• Can you define and Configure a Power Pages Site without using the exact wording of an API/reference page?
• Can you identify the boundary where and Configure a Power Pages Site 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 and Configure a Power Pages Site

• and Configure a Power Pages Site 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 Pages 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.

Official references for deeper lookup

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 Pages documentation
• Power Apps documentation
• Power Automate documentation
• Power BI documentation
• Power Platform developer documentation