{"id":11151,"date":"2015-10-01T07:22:00","date_gmt":"2015-10-01T07:22:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2015\/10\/01\/how-to-use-wmf-4-with-azure-dsc-extension-in-azure-cloud-service-manager-asm\/"},"modified":"2019-03-05T08:38:38","modified_gmt":"2019-03-05T16:38:38","slug":"how-to-use-wmf-4-with-azure-dsc-extension-in-azure-cloud-service-manager-asm","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/how-to-use-wmf-4-with-azure-dsc-extension-in-azure-cloud-service-manager-asm\/","title":{"rendered":"How to use WMF 4 with Azure DSC Extension in Azure Cloud Service Manager (ASM)"},"content":{"rendered":"
\n

Overview<\/h2>\n

In version 2.7 of the Azure DSC Extension, we added support to leave your Virtual Machine on the latest supported version of WMF 4.0. This blog will show you how to use this feature in Azure Cloud Service Manager (ASM). This assumes you already know how to create a VM in the Azure PowerShell SDK. If you don’t please see MSDN<\/a>. We are working to add this feature into the Azure Powershell SDK DSC extension Cmdlets directly. Currently, the WMF 4 feature is only available if you form the JSON yourself and send it to the extension using the generic extension Cmdlet.\nIn this Example I will show you:<\/p>\n

    \n
  1. How to Create the JSON you need to send to the extension.<\/li>\n
  2. How to create URI to published configuration which will only let people with this URI access it, known as the `ModulesUrl’ to the extension.<\/li>\n
  3. How to send this JSON to the extension on an existing VM.<\/li>\n<\/ol>\n

    Creating the JSON<\/h2>\n

    To do this, use the Set-AzureVMExtension<\/code> Cmdlet rather than the Set-AzureVMDscExtension<\/code> Cmdlet and pass the JSON using the -PublicConfiguration<\/code> parameter. The following function New-XAzureVmDscExtensionJson<\/code> will create the JSON needed for this example.<\/p>\n

    \n
    # Create a Json to send the the DSC VM Extension\r\nfunction New-XAzureVmDscExtensionJson\r\n{\r\n[CmdletBinding()]\r\n    param(\r\n        [Parameter(Mandatory = $true)]\r\n        [ValidateNotNullOrEmpty()]\r\n        [string]\r\n        $moduleName,\r\n        [Parameter(Mandatory = $false)]\r\n        [ValidateNotNull()]\r\n        [string]\r\n        $modulesUrl,\r\n        [AllowNull()]\r\n        [HashTable]\r\n        $properties,\r\n        [Parameter(Mandatory = $true)]\r\n        [ValidateNotNullOrEmpty()]\r\n        [string]\r\n        $configurationName,\r\n        [Parameter(Mandatory = $true)]\r\n        [ValidateNotNullOrEmpty()]\r\n        [ValidateSet('4.0','latest','5.0PP')]\r\n        [string]\r\n        $WmfVersion\r\n    )\r\n    $publicSettingsTable = @{\r\n        Properties = $properties\r\n        WmfVersion = $WmfVersion\r\n    }\r\n    if($null -ne $modulesUrl)\r\n    {\r\n      $publicSettingsTable.Add('ModulesUrl',$modulesUrl)\r\n    }\r\n    $publicSettingsTable.Add('ConfigurationFunction' , \"${ModuleName}\\${configurationName}\")\r\n    return ConvertTo-Json -Depth 8 $publicSettingsTable\r\n}<\/pre>\n
     <\/p>\n<\/div>\n
    Here is an explanation of the values:<\/p>\n