.DESCRIPTION Azure Automation runbook script to tag an standalone SAP Java Application Server Instance on Linux VM.

.VERSION 0.0.2

.GUID ef6b15e1-1e53-4251-b512-650d2753ed55

.AUTHOR Goran Condric


.COPYRIGHT (c) 2020 Microsoft . All rights reserved.

.TAGS Azure Automation SAP Java Application Server Instance Linux Tag Standalone Runbook







0.0.1: - Add initial version
0.0.2: - Support for using a system-assigned managed identity for an Azure Automation account, and multiple Azure subscriptions

#Requires -Module SAPAzurePowerShellModules

[string] $ResourceGroupName,

[string] $VMName,

[Parameter(Mandatory=$True, HelpMessage="SAP System <SID>. 3 characters , starts with letter.")] 
[string] $SAPSID,

[Parameter(Mandatory=$True, HelpMessage="SAP Java Application Server Instance Number")]
[ValidateLength(1, 2)]
[string] $SAPJavaApplicationServerInstanceNumber,

[Parameter(Mandatory=$false, HelpMessage="Subscription ID. If null, the current subscription of automation account is used instead.")] 
[string] $SubscriptionId


Write-WithTime "Make sure to enable appropriate RBAC permissions to the system identity of this automation account. Otherwise, the runbook may fail."

Write-Output ""
Write-Output "You can enable system identity on the Azure automation account:"
Write-Output "1. Go to: Azure automation acccount -> Identity -> System asigned -> Status -> <On>"
Write-Output "2. Go to: Azure automation acccount -> Identity -> System asigned -> Permissions -> Azure role assignments -> Add role assignment ->"
Write-Output "Scope: 'Subscription'"
Write-Output "Subscription: <Chose your Subscription>"
Write-Output "Role: 'Owner'"
Write-Output ""
Write-Output "More info on: https://docs.microsoft.com/en-us/azure/automation/enable-managed-identity-for-automation#assign-role-to-a-system-assigned-managed-identity "
Write-Output ""

# Connect to Azure with Automation Account system-assigned managed identity
Write-WithTime " Connecting to Azure with Automation Account system-assigned managed identity ...."
Write-Output ""

# Ensures you do not inherit an AzContext in your runbook
Disable-AzContextAutosave -Scope Process | out-null

try {
    # Connect to Azure with system-assigned managed identity
    $AzureContext = (Connect-AzAccount -Identity).context
    Write-Error "There is no system-assigned user identity. Aborting."; 
    Write-Error  $_.Exception.Message

if ($SubscriptionId){
    Write-Output "Using specified Subscription ID '$SubscriptionId'."
    $SubscriptionId = $SubscriptionId.trim()
    Select-AzSubscription -SubscriptionId $SubscriptionId -ErrorVariable -notPresent  -ErrorAction SilentlyContinue -Tenant $AzureContext.Tenant

# set and store context
$AzureContext = Set-AzContext -SubscriptionName $AzureContext.Subscription -DefaultProfile $AzureContext 

$ResourceGroupName          = $ResourceGroupName.Trim()
$VMName                     = $VMName.Trim()
$SAPSID                     = $SAPSID.Trim()
$SAPJavaApplicationServerInstanceNumber    = $SAPJavaApplicationServerInstanceNumber.Trim()

# Check if resource group exists. If $False exit
Confirm-AzResoureceGroupExist -ResourceGroupName $ResourceGroupName 

# Check if VM. If $False exit
Confirm-AzVMExist -ResourceGroupName $ResourceGroupName -VMName $VMName

New-AzSAPSystemSAPJavaApplicationServerInstanceLinuxTags -ResourceGroupName $ResourceGroupName -VMName $VMName -SAPSID $SAPSID -SAPApplicationInstanceNumber $SAPJavaApplicationServerInstanceNumber

Write-WithTime "Tagging of VM '$VMName' in resource group '$ResourceGroupName' with tags: SAPSID='$SAPSID' ; SAPApplicationInstanceNumber='$SAPJavaApplicationServerInstanceNumber' ; SAPApplicationInstanceType='SAP_J' done."