Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
All new connectors that are introduced by Microsoft and partners to Power Platform are disabled by default for customers operating in the following US government clouds: Government Community Cloud - High (GCC High) and Department of Defense (DoD). Administrators can review these new connectors before authorizing their use across the organization in the Data policy page of the Power Platform admin center. Connectors already published in GCC High and DoD remain enabled.
Power Platform and third parties continuously release new connectors and administrators can set a default classification for those connectors via its data policies. Depending on how these data policies are configured within the customer's tenant, new connectors can unintentionally become available to makers in certain environments without administrators approving their use. Such occurrences must be avoided in US government clouds where strict compliance is mandated. Administrators can rely on this safeguard mechanism in GCC High and DoD to better control the use of connectors.
Note
Custom connectors can't be disabled with this new data policy control.
When a connector is disabled, administrators can still classify and configure the connector in the data policies, but its use is blocked in Power Apps and Power Automate.
Prerequisites
New connectors are only disabled by default for the following US government clouds:
- Government Community Cloud - High (GCC High)
- Department of Defense (DoD)
Review new connectors disabled by default
Take these steps to review a connector disabled by default, change a connector setting, and test ability to add a connector to an app.
Step 1: View the new connector
Select the Data policies tab where all data policies are located.
Select Enable connectors in the toolbar.
New connectors (those that haven't been reviewed) have the status Mark as reviewed.
Connectors that have already been reviewed and authorized have the status Reviewed.
Step 2: Enable the new connector or let it remain disabled
If you want to keep the connector disabled, select Mark as reviewed.
If you want to enable the connector, select the Enable toggle.
In both cases, the status is changed to Reviewing.
Select Save. The status of the connector is now set to Reviewed.
Step 3: View a disabled connector in a data policy
Select a data policy in the Data policies page.
Consult the Prebuilt connectors tab. Connectors that are disabled have the status Disabled.
Step 4: Attempt to add a disabled connector in a Power App
Open any Power App.
Add a disabled connector to a flow. An error message appears.
Note
This new tenant-level setting is also enforced on existing apps and flows that were built using connectors that are now disabled.
PowerShell support
The new data control has the following structure in PowerShell. The connectorSettings object is an array of connectors specifying whether it's enabled or disabled (behavior) and whether it has been reviewed or not (isReviewed).
$connectorBlockingDefinition = [pscustomobject] @{
ConnectorSettings= @(
[pscustomobject] @{
id # connectorId -- string
behavior # connector behavior -- "Allow"/"Deny"
isReviewed # whether connector has been reviewed -- boolean
}
)
}
Retrieve the existing connector blocking policy for the tenant
Get-PowerAppDlpConnectorBlockingPolicies
Example:
Get-PowerAppDlpConnectorBlockingPolicies -TenantId "aaaabbbb-0000-cccc-1111-dddd2222eeee"
The above cmdlet outputs the connectors that are blocked/allowed for the evaluation and the policyId.
Create a new connector blocking policy for the tenant
New-PowerAppDlpConnectorBlockingPolicy –TenantId "aaaabbbb-0000-cccc-1111-dddd2222eeee" -ConnectorBlockingDefinition $connectorBlockingDefinition
Where $connectorBlockingDefinition = [pscustomobject] @{
ConnectorSettings= @
[pscustomobject] @{
id = "/providers/Microsoft.PowerApps/apis/connector1"
behavior = "Allow"
isReviewed = $true
},
[pscustomobject] @{
id = "/providers/Microsoft.PowerApps/apis/connector2"
behavior="Deny"
IsReviewed=$false
}
)
}
Update the connector blocking policy for the tenant
Set-PowerAppDlpConnectorBlockingPolicy -TenantId "aaaabbbb-0000-cccc-1111-dddd2222eeee" -PolicyId "1aaaaaa1-2bb2-3cc3-4dd4-5eeeeeeeeee5" -ConnectorBlockingDefinition $connectorBlockingDefinition
Fetch the connector blocking policy using the policyId
Get-PowerAppDlpConnectorBlockingPolicy -TenantId "aaaabbbb-0000-cccc-1111-dddd2222eeee" -PolicyId "1aaaaaa1-2bb2-3cc3-4dd4-5eeeeeeeeee5"