SqlServiceAccount: Not working for IntegrationServices, SQLServerBrowser and Fulltext

Details of the scenario you tried and the problem that is occurring

I tried to work with SqlServiceAccount but it is not working as I expected because I can't set service account for IntegrationServices, SQLServerBrowser and Fulltext service.

The error : PowerShell DSC resource MSFT_SqlServiceAccount failed to execute Test-TargetResource functionality with error message: System.Exception: Service type 'IntegrationServices' is not instance aware.

Same error happens with IntegrationServices, SQLServerBrowser and Fulltext service.
I don't understand why the property is giving me the choice of those services if I can't use the resource with them.

The DSC configuration that is using the resource (as detailed as possible)

                SqlServiceAccount integration 
                {
                    ServerName           = $NodeName
                    InstanceName         = $Node.InstanceName
                    ServiceType          = "IntegrationServices"
                    ServiceAccount       = $Node.SqlAgentServiceCredential
                 #   RestartService       = $true
                 #   Force                = $true   
                    DependsOn   = $InstallTask

                }

Version of the operating system and PowerShell the target node is running

Windows 2016

SQL Server edition and version the target node is running

Edition : Standard Edition
Version : 11.4.7001.0
Language : 1033

What SQL Server PowerShell modules, and which version, are present on the target node.

xSqlServer 9.1.0.0
SQLASCMDLETS 1.0
SQLPS 1.0

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

SqlServerDsc 11.3.0.0

Start with the MSFT_SqlServiceAccount resource and its ServiceType handling, focusing on IntegrationServices, SQLServerBrowser, and Fulltext. Compare the service types exposed by the resource with the instance-awareness validation and existing coverage; done means the supported behavior is consistent and these configurations no longer fail unexpectedly.