For those of you who have been trying to automate anything related to Microsoft Teams, let me tell you that there is a new PowerShell Module in town: Microsoft Teams 0.9.0 which you can install with the following command:
Install-Module MicrosoftTeams Now to automate the channel creation In A Team you can simply:
In this post I’ll show you how to Use PowerShell to enable Azure Storage Account Firewall Rules.
Be sure to be have AzureRM PowerShell 4.4.1 module installed.
Login to your Azure Account # Launch Powershell and start by Login to your Azure Account.
In this post I’ll show you how to Use PowerShell to Enable and Automate Azure Analysis Backup.
Enable Azure Analysis Service Backup # Enable-AzureRmAnalysisServicesBackup is a small powershell script that uses the the Set-AzureRmResource cmdlet to enable backup location to an Azure Analysis Service instance.
Last week, firewall support was added to Azure Analysis Service (https://azure.microsoft.com/en-us/blog/azure-analysis-services-adds-firewall-support/). The thing is that, at the time of writing, there is no AzureRM cmdlet available to Use PowerShell to Enable Azure Analysis Services Firewall
So, with the help of Resource Explorer I found which properties must be added to the service (resource) in order to enable the firewall:
This week I had to repeat the process of creating a Service Principal in order to use the Microsoft.Azure.Management.Fluent lib with .NET Core so I decided it was time to script the process. With the following script you can Create a Service Principal and write required parameters to a .azureauth file.
HDInsight: Scale Horizontally with Scale-HDInsightClusterNodes.ps1 a PowerShell workflow that will help you automate the process of scaling your cluster.
The script receives 4 parameters:
ResourceGroupName: The name of the resource group where the cluster resides ClusterName: The name of your HDInsight cluster Nodes: The number of nodes you want for the cluster ConnectionName: The name of your automation connection account and requires the following PowerShell modules: AzureRM.Profile, AzureRM.HDInsight
Recently I client ask me to enable application and http logging for more than 20 AzureRM Web Apps. Furthermore the client wanted the logs to be stored in a Storage Account.
Issues started when I decided to Use PowerShell to Enable Logging for Azure RM Web Apps, because there is no equivalent to the ASM Enable-AzureWebsiteApplicationDiagnostic cmdlet for ARM resources.
Last week I wrote: Step by step: Running ASP.NET Core on Raspberry Pi and didn’t have the time to write about running the application on startup.
After browsing for a while I found this great post: Windows IoT Core: Running a PowerShell Script on Startup which showed me the way!
As a prerequisite read and run the sample provided here: Step by step: Running ASP.NET Core on Raspberry Pi
Stop or Start all WebApps in your Azure subscription with Stop-Start-All-WebApps.ps1 a simple PowerShell workflow runbook that will help you automate the process of stopping or starting every single WebApp (Website) you’ve deployed.
The script receives two required parameters:
Stop: If set to true stop the WebApps (Websites) otherwise start the WebApps (Websites) CredentialAssetName: The name of a valid Credential Asset (AutomationPSCredential) you must have previously configured. As you can see below, the script is quite simple and uses the following PowerShell Activities and Cmdlets:
In this post I’ll just show the list of PowerShell commands needed to Create an Azure Site to Site VPN and give you some tips when using a Check Point Security Gateway.
First things first! so if you have not installed and configured Azure PowerShell go for it: How to install and configure Azure PowerShell
One of the great things about Azure is the possibility to Export Azure Resource Groups Templates. Each template is a json file containing the exact configuration of the services you’ve provisioned in a Resource Group.
Using this templates you can treat your Infrastructure as code and repeatedly deploy your application during every stage of the application lifecycle in the same way, each and every time.