Fix DLP Impact Analysis app to filter deleted environments when copying policies

[Copilot]

The DLP Impact Analysis app's copy policy function includes deleted environments in the new policy because it passes the source policy's environment list directly to the API without validation.

Changes

• Canvas App Fix: Modified admin_dlpimpactanalysis_4dfb8_DocumentUri.msapp copy button handler to filter environments against active environments in Dataverse before API call

  // Before: directly uses source policy environments
  environments: dlDLPPolicies.Selected.environments
  
  // After: filters against col_environments (active only)
  ClearCollect(
      col_tempEnvsToCopy,
      Filter(dlDLPPolicies.Selected.environments, name in col_environments.Name)
  );
  PowerPlatformforAdmins.CreatePolicyV2({
      ...
      environments: col_tempEnvsToCopy
  })
  

• Documentation: Added .github/ISSUE_GUIDANCE/dlp-impact-analysis-copy-deleted-environments.md with root cause analysis, workarounds, and testing procedures

Behavior Change

Copied DLP policies now exclude environments that have been deleted from the tenant. This aligns Copy functionality with existing Edit functionality which already implements this filter.

Workaround for v4.47.1

Users on current version can use Edit → Save as Draft → Create new policy, or copy policies via Power Platform Admin Center.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[CoE Starter Kit - BUG] Discrepancies when creating a copy of a DLP policy using the DLP Impact Analysis Application</issue_title>
<issue_description>### Does this bug already exist in our backlog?

• I have checked and confirm this is a new bug.

Describe the issue

Hi Power CAT Team,

Good day!

This is to bring about an issue that we have identified upon using the DLP Impact Analysis App as part of the Core Components in the CoE Toolkit.

It seems that when a new Environment has been created or an Environment has been deleted in the Power Platform Tenant, deleted environments are still included in the list upon trying to create a copy of an existing DLP policy using the DLP impact analysis app.

You may refer to the attached word document for the testing I have conducted in our Q/Test tenant.

Discrepancies in the DLP Impact Analysis App.docx

I am also happy to discuss and do a quick connect and screenshare of the steps I did in the Q tenant.

Looking forward for your response.

Expected Behavior

We are expecting that upon creation of the duplicate DLP policy using the DLP Impact Analysis App, it will create an exact copy of its settings.

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.47.1

What app or flow are you having the issue with?

Data Policy Impact Analysis

What method are you using to get inventory and telemetry?

None

Steps To Reproduce

No response

Anything else?

No response</issue_description>

<agent_instructions>Discrepancies when creating a copy of a DLP policy using the DLP Impact Analysis Application. Please provide the guidance and suggestion on this </agent_instructions>

Comments on the Issue (you are @copilot in this section)

Custom agent used: CoE Custom Agent
Specialized agent for triaging and fixing issues in the CoE Starter Kit. Always consult the official CoE docs and the team’s SharePoint notes first, then mine prior GitHub issues and the CoE Common Responses playbook.

• Fixes [CoE Starter Kit - BUG] Discrepancies when creating a copy of a DLP policy using the DLP Impact Analysis Application #10617

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.