<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rss/1.0/modules/syndication/" xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:wfw="https://wellformedweb.org/CommentAPI/" xmlns:slash="https://purl.org/rss/1.0/modules/slash/"
  version="2.0">
  <channel>
    <title>Kanwartej Basrai’s Blog</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/kbasrai/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/kbasrai/feed.xml</link>
    <description>My ramblings on SharePoint and other things.</description>
    <lastBuildDate>Wed, 17 Apr 2019 03:41:27 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>How to use a different version of DSC modules available in Azure DSC Module Gallery</title>
      <link>https://docs.microsoft.com/archive/blogs/kbasrai/azure-automation-dsc-module-versions</link>
      <pubDate>Thu, 03 May 2018 12:13:21 GMT</pubDate>
      <dc:creator><![CDATA[Kanwartej Basrai]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/kbasrai/?p=45</guid>
      <description><![CDATA[The Azure team updates the Azure DSC module gallery regularly and there is also mechanism provided...]]></description>
      <content:encoded><![CDATA[The Azure team updates the <a href="https://docs.microsoft.com/en-us/azure/automation/automation-update-azure-modules">Azure DSC module gallery</a> regularly and there is also mechanism provided in the Azure Automation account to update the modules when new version are available. But how do you use a different or an older version of these modules? Recently I came across a scenario where I needed to use an older version of DSC module for SharePoint farm build as all the testing had been done against a specific version. The modules available in the gallery had already advanced to the latest SharePointDSC module. Following is a guide on how to use specific version of DSC modules. These steps also apply if you built your own module, and wanted to import it into your Automation account.
<h2>Deploy directly from the PowerShell Gallery</h2>
<ol>
 	<li>Go to <a href="https://www.powershellgallery.com/">https://www.powershellgallery.com/</a> and search for the module you are require - in my case it was SharePointDSC.</li>
 	<li>Navigate to the bottom of the page where it shows all the previous releases<a href="https://msdnshared.blob.core.windows.net/media/2018/05/moduleVersions.png">
<img width="300" height="168" class="alignnone size-medium wp-image-55" alt="" src="https://msdnshared.blob.core.windows.net/media/2018/05/moduleVersions-300x168.png" /></a></li>
 	<li>Click "Deploy to Azure Automation". This will redirect you to the Azure portal, and once you successfully login, it will navigate you to Import Module Blade.
<a href="https://msdnshared.blob.core.windows.net/media/2018/05/importblade.png"><img width="300" height="206" class="alignnone size-medium wp-image-65" alt="" src="https://msdnshared.blob.core.windows.net/media/2018/05/importblade-300x206.png" /></a></li>
 	<li>Here you can either select an existing automation account to import the module to, or create a new one.</li>
</ol>
<h2>Manual Import</h2>
To manually import the module
<ol>
 	<li>Save the module to a local directory by running save Save-Module Commandlet

[code language="powershell"]Save-Module -Name SharePointDSC -Path [Path] -RequiredVersion 2.1.0.0[/code]

</li>
 	<li>Navigate it to the path where you saved the module, and open the <em>&lt;moduleName&gt;\&lt;Version&gt;</em> folder. The <em>&lt;version&gt;</em> folder contains the ps1 file with module definition.</li>
 	<li>Zip all the contents of this folder and name the zip file same as the name of the ps1 file. So in my case, the file is called <strong>SharePointDSC.zip
</strong>Here is some guidance on naming module files. This also applies if you were building a custom module <a href="https://azure.microsoft.com/en-us/blog/authoring-integration-modules-for-azure-automation/">https://azure.microsoft.com/en-us/blog/authoring-integration-modules-for-azure-automation/</a></li>
 	<li>Once you have a zip file, Login into the azure portal and navigate to the Automation account, and then to the DSC modules blade
<a href="https://msdnshared.blob.core.windows.net/media/2018/05/ModulesBlade.png"><img width="285" height="300" class="alignnone size-medium wp-image-75" alt="" src="https://msdnshared.blob.core.windows.net/media/2018/05/ModulesBlade-285x300.png" /></a></li>
 	<li>Click "<strong>Add a Module</strong>" and upload the zip file. Once the importing of the module is finished, the module is ready for use.</li>
</ol>]]></content:encoded>
    </item>
    <item>
      <title>Hello world!</title>
      <link>https://docs.microsoft.com/archive/blogs/kbasrai/hello-world</link>
      <pubDate>Tue, 12 Jan 2016 08:27:44 GMT</pubDate>
      <dc:creator><![CDATA[Kanwartej Basrai]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/kbasrai/?p=1</guid>
      <description><![CDATA[Hi and welcome to my new blog.

I am a Canberra based Consultant with Microsoft Consulting...]]></description>
      <content:encoded><![CDATA[Hi and welcome to my new blog.

I am a <a title="Canberra" href="https://binged.it/1Zrk1k9" target="_blank">Canberra</a> based Consultant with Microsoft Consulting Services. My focus area is SharePoint and has been for a number of years. I love working with customers to help them solve their Collaboration, Content management, Document management etc. needs with SharePoint. Apart from SharePoint I also have experience in and have a passion for other Microsoft development technologies.

In this blog, I aim to share my experiences and learnings with the wider world and learn more along the way.

Happy reading :)]]></content:encoded>
    </item>
  </channel>
</rss>