{"id":1701,"date":"2014-04-25T15:04:00","date_gmt":"2014-04-25T15:04:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2014\/04\/25\/understanding-import-dscresource-keyword-in-desired-state-configuration\/"},"modified":"2019-02-18T13:05:20","modified_gmt":"2019-02-18T20:05:20","slug":"understanding-import-dscresource-keyword-in-desired-state-configuration","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/understanding-import-dscresource-keyword-in-desired-state-configuration\/","title":{"rendered":"Understanding Import-DscResource Keyword in Desired State Configuration"},"content":{"rendered":"
\n

Desired State Configuration resources are used to model and change the state of different components of the system. In an earlier <\/span>blog post<\/a><\/span>, we discussed details about deploying and discovering those resources and introduced Import-DscResource<\/strong> dynamic keyword. In this post, we will discuss some more details about the usage and internal working of this dynamic keyword.  This keyword is only available inside configuration block. Its syntax looks like PowerShell cmdlet but it’s not a cmdlet and behaves differently.  <\/span><\/p>\n

 <\/p>\n

When authoring the DSC configuration in ISE, the PowerShell parser, provides IntelliSence for resources and resource properties by auto loading the resource definitions from $pshome module path. Moreover, the same resource definitions are used during compilation step (generation of MOF document) to validate the entries of the configuration. E.g. resource schema validation is done for following:<\/span><\/p>\n