Introduction

The xAzurePack module contains resources for installation and configuration of Windows Azure Pack.

This module includes 8 DSC resources that automate provisioning of resources in Microsoft Azure.

All of the resources in the DSC Resource Kit are provided AS IS, and are not supported through any Microsoft standard support program or service. The ""x" in xAzure stands for experimental, which means that these resources will be fix forward and monitored by the module owner(s).

Please leave comments, feature requests, and bug reports in the Q & A tab for this module.

If you would like to modify xAzurePack module, feel free. When modifying, please update the module name, resource friendly name, and MOF class name (instructions below). As specified in the license, you may copy or modify this resource as long as they are used on the Windows Platform.

For more information about Windows PowerShell Desired State Configuration, check out the blog posts on the PowerShell Blog (this is a good starting point). There are also great community resources, such as PowerShell.org, or PowerShell Magazine. For more information on the DSC Resource Kit, check out this blog post.

Installation

To install xAzurePack module

To confirm installation:

Requirements

This module requires at least the latest version of PowerShell (v4.0, which ships in Windows 8.1 or Windows Server 2012R2). To easily use PowerShell 4.0 on older operating systems, install WMF 4.0. Please read the installation instructions that are present on both the download page and the release notes for WMF 4.0.

Details

xAzurePackSetup resource has following properties:

xAzurePackUpdate resource has following properties:

xAzurePackAdmin resource has following properties:

xAzurePackFQDN resource has following properties:

xAzurePackDatabaseSetting resource has following properties:

xAzurePackIdentityProvider resource has following properties:

xAzurePackRelyingParty resource has following properties:

xAzurePackResourceProvider resource has following properties:

Renaming Requirements

When making changes to these resources, we suggest the following practice:

  1. Update the following names by replacing MSFT with your company/community name and replacing the "x" with "c" (short for "Community") or another prefix of your choice:
    • Module name (ex: xAzurePack becomes cAzurePack)
    • Resource folder (ex: MSFT_xAzureQuickVM becomes Contoso_cAzureQuickVM)
    • Resource file name (ex: MSFT_xAzureQuickVM becomes Contoso_cAzureQuickVM)
    • Resource Friendly Name (ex: xAzureQuickVM becomes cAzureQuickVM)
    • MOF class name (ex: MSFT_xAzureQuickVM becomes Contoso_cAzureQuickVM)
    • Filename for the <resource>.schema.mof (ex: MSFT_xAzureQuickVM.schema.mof becomes Contoso_cAzureQuickVM.schema.mof)
  2. Update module and metadata information in the module manifest
  3. Update any configuration that use these resources

We reserve resource and module names without prefixes ("x" or "c") for future use (e.g. "MSFT_**RealResourceName**" or "**RealResourceName**"). If the next version of Windows Server ships with a "**RealResourceName**" resource, we don't want to break any configurations that use any community modifications. Please keep a prefix such as "c" on all community modifications.

Versions

1.0.0.0

Initial release with the following resources

Examples

An example configuration is included in the Examples folder within the module, which also uses the xSQLServer module and xCredSSP modules

AzurePack-SeperateSQL.ps1 installs all Azure Pack admin and tenant servers and SQL on a seperate server.