<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>powershell on bramstoop.com</title>
    <link>https://www.bramstoop.com/tags/powershell/</link>
    <description>Recent content in powershell on bramstoop.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Sep 2019 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.bramstoop.com/tags/powershell/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Monitor Sitecore certificates and RunAsAccount(s) using Azure Automation</title>
      <link>https://www.bramstoop.com/posts/2019/09/2019-09-16-monitor-sitecore-certificates-and-runasaccount-azure-automation/</link>
      <pubDate>Mon, 16 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2019/09/2019-09-16-monitor-sitecore-certificates-and-runasaccount-azure-automation/</guid>
      <description>BACK TO BLOG OVERVIEW
 Using the instructions underneath you will be able to import an Azure Automation runbook that will alert you using Sendgrid before certificates will expire.
The urge of creating this script was to find a way to inform us whenever the private certificate for Sitecore X-connect would expire. The script will, however, help you to monitor all your certificates within your Azure subscription. Next to that it will assure you will renew the certificates for your RunAsAccounts, causing it not to expire, so that your runbooks will be operational.</description>
    </item>
    
    <item>
      <title>Disabling Sitecore config files in Azure App Service using Azure DevOps</title>
      <link>https://www.bramstoop.com/posts/2018/10/2018-10-22-disabling-sitecore-config-files-in-azure-app-service-using-azure-devops/</link>
      <pubDate>Mon, 22 Oct 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/10/2018-10-22-disabling-sitecore-config-files-in-azure-app-service-using-azure-devops/</guid>
      <description>BACK TO BLOG OVERVIEW
 Since we are keen on keeping the Sitecore scwdp packages OOTB as untouched as can be (as of our deployment strategy) we have two type of tasks in our release pipeline to disable/rename config files after deploying a vanilla package. Please keep in mind that, while using these tasks, we are always deploying to a staging slot with status &amp;lsquo;stopped&amp;rsquo;.
 While checking the script(s), note that you are able to write your own powershell scripts within the $commandBody variable: &amp;quot;$commandBody = @{ command = &amp;quot;powershell.</description>
    </item>
    
    <item>
      <title>Monitor your Azure SSL certificate expiration</title>
      <link>https://www.bramstoop.com/posts/2018/08/2018-08-03-monitor-your-azure-ssl-certificates-expiration/</link>
      <pubDate>Fri, 03 Aug 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/08/2018-08-03-monitor-your-azure-ssl-certificates-expiration/</guid>
      <description>BACK TO BLOG OVERVIEW
 Using the instructions underneath you will be able to import an Azure Automation runbook that will alert you using Sendgrid whenever certificates will expire.
The urge of creating this script was to find a way to inform us whenever the private certificate for Sitecore X-connect would expire. The script will, however, help you to monitor all your certificates within your Azure subscription.
Prerequisites: - Azure Automation account - Azure Automation module - AzureRM.</description>
    </item>
    
    <item>
      <title>Replacing the Sitecore client certificate on Azure in 5 steps</title>
      <link>https://www.bramstoop.com/posts/2018/06/2018-06-13-replacing-the-sitecore-client-certificate-on-azure-in-5-steps/</link>
      <pubDate>Wed, 13 Jun 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/06/2018-06-13-replacing-the-sitecore-client-certificate-on-azure-in-5-steps/</guid>
      <description>BACK TO BLOG OVERVIEW
 These instructions are for a Sitecore 9.0.1. XP1 Topology - on Azure.
For using X-connect there is a need of using client certificates. In Azure these certificates are named private certificates. Since these certificates expire there is a need to replace them.
To make life easier I will describe this process in the 5 steps underneath:
Step 1 Upload the new certificate (pfx) to Azure using ARM template or portal.</description>
    </item>
    
    <item>
      <title>Download Sitecore media items to local disk</title>
      <link>https://www.bramstoop.com/posts/2018/06/2018-06-08-download-sitecore-media-items-to-local-disk/</link>
      <pubDate>Fri, 08 Jun 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2018/06/2018-06-08-download-sitecore-media-items-to-local-disk/</guid>
      <description>BACK TO BLOG OVERVIEW
 For one of our customers we were in need of downloading all media files from Sitecore to our local hard disk. Since we are using the Sitecore SPE extension, the following script gave us all the urls we needed to download them using our local Powershell.
 [code language=&amp;quot;powershell&amp;rdquo;] $url = &amp;ldquo;https://URLOFTHESITECOREWEBSITE/&amp;rdquo; $mediaLibraryRootPath = &amp;ldquo;master:/sitecore/media library/Images/&amp;rdquo; $listAllItems = Get-ChildItem -Recurse $mediaLibraryRootPath
foreach($item in $listAllItems){</description>
    </item>
    
    <item>
      <title>Sitecore hardening using Azure App Authentication</title>
      <link>https://www.bramstoop.com/posts/2017/08/2017-08-11-sitecore-hardening-using-azure-app-authentication/</link>
      <pubDate>Fri, 11 Aug 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2017/08/2017-08-11-sitecore-hardening-using-azure-app-authentication/</guid>
      <description>BACK TO BLOG OVERVIEW
  With Azure App Authentication it is easy to secure your app with an identity provider. The steps to take are described at the following page: https://docs.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-how-to-configure-active-directory-authentication .
For securing certain url paths it is required to set Action to take when request is not authenticated to Allow request (no action).
When you have followed the instructions above, the next step is to create a authorization.</description>
    </item>
    
    <item>
      <title>ipSecurityRestrictions on Azure App Services</title>
      <link>https://www.bramstoop.com/posts/2017/07/2017-07-16-ipsecurityrestrictions-on-azure-app-services/</link>
      <pubDate>Sun, 16 Jul 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.bramstoop.com/posts/2017/07/2017-07-16-ipsecurityrestrictions-on-azure-app-services/</guid>
      <description>BACK TO BLOG OVERVIEW
  With the powershell scripts underneath you can easily close and open traffic towards your azure app services. Note: by adjusting the resource name variable you can add appsettings to your staging slot as well.
 [expander_maker id=&amp;quot;1&amp;rdquo; more=&amp;quot;Script: open to the world&amp;rdquo; less=&amp;quot;Collapse&amp;rdquo;] ### Open to the world ### Write-Host &amp;ldquo;Open all traffic to app service&amp;rdquo; $resourceGroupName = &amp;lsquo;TOBEFILLED&amp;rsquo; $resourceName = &amp;lsquo;YOURAPPNAMEHERE&amp;rsquo; + &amp;lsquo;/web&amp;rsquo; $r = Get-AzureRmResource -ResourceGroupName $resourceGroupName -ResourceType Microsoft.</description>
    </item>
    
  </channel>
</rss>