SqlPermission: Should Be Cluster Aware

Details of the scenario you tried and the problem that is occurring:
When the xSQLServerPermission resource is applied to all of the nodes in a Failover Cluster Instance (FCI), all of the nodes will connect to the instance and ensure the desired state is true even if the node is not currently hosting the instance.

The DSC configuration that is using the resource (as detailed as possible):
When the following configuration is applied to two or more nodes in a FCI.

xSQLServerPermission 'SQLConfigureServerPermission-ClusSvc'
{
    Ensure               = 'Present'
    NodeName             = 'SQLNODE01.company.local'
    InstanceName         = 'MSSQLSERVER'
    Principal            = 'NT SERVICE\ClusSvc'
    Permission           = 'AlterAnyAvailabilityGroup', 'ViewServerState'

    PsDscRunAsCredential = $SysAdminAccount
}

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Any

What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
Any

Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Any

Start by locating the xSQLServerPermission resource and reviewing how it connects to a SQL Server instance in the FCI scenario described. Verify the behavior when the target node is not hosting the instance, and consider the work complete when applying the resource across FCI nodes only manages the active instance host.