Azure Automation and Logic Apps for scheduled auto-scaling of Function App

I'm trying to create an Azure automation system to change the number of always ready instances of a Function App (the App Service Plan is Elastic Premium One EP1):

The Automation System is created in order to set the number of Always Ready Instances to 3 during week days, and set it to 1 during weekend days.

The System is composed by the following two runbooks created under the service Azure Automation Accounts:

1. "runbook-Weekdays"

<!-- begin snippet: js hide: false console: true babel: false -->

<!-- language: lang-js -->

$resourceGroupName = "xxxxxxxxxxxx"
$functionApp = "xxxxxxxxxx-func"

$Resource = Get-AzResource -ResourceGroupName $resourceGroupName -ResourceName $functionApp/config/web -ResourceType Microsoft.Web/sites
$Resource.Properties.minimumElasticInstanceCount = 3
$Resource | Set-AzResource -Force

<!-- end snippet -->

2. "runbook-Weekend-days"

<!-- begin snippet: js hide: false console: true babel: false -->

<!-- language: lang-js -->

$resourceGroupName = "xxxxxxxxxxxx"
$functionApp = "xxxxxxxxxxxx-func"

$Resource = Get-AzResource -ResourceGroupName $resourceGroupName -ResourceName $functionApp/config/web -ResourceType Microsoft.Web/sites
$Resource.Properties.minimumElasticInstanceCount = 1
$Resource | Set-AzResource -Force

<!-- end snippet -->

Note that I'm using a "System Assigned" identity in my Automation Account.

While the automation logic is implemented using Azure Logic Apps:

Where the expression under the "Condition" box is: formatDateTime(utcNow(),'dddd'), which set only for the week days as can be seen from the previous figure.

The following figure is the second part of the Logic App:

Note that, when creating the Automation Job in Logic Apps, I have selected "OAuth default" as authentication method, then I simply pasted the tenantID of my subscription.

Now, if I test the Logic App from the Logic App service, it works:

And I would expect a number of always ready instances equal to 3, but if I check the number of always ready instances, nothing changed:

Also, going to the errors page of the runbook page:

I see the following two errors:

<!-- begin snippet: js hide: false console: true babel: false -->

<!-- language: lang-js -->

Get-AzResource : Run Connect-AzAccount to login. At line:4 char:13 + $Resource = Get-AzResource -ResourceGroupName $resourceGroupName -Res ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : CloseError: (:) [Get-AzResource], PSInvalidOperationException + FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.GetAzureResourceCmdlet

<!-- end snippet -->

and

<!-- begin snippet: js hide: false console: true babel: false -->

<!-- language: lang-js -->

The property 'minimumElasticInstanceCount' cannot be found on this object. Verify that the property exists and can be set. At line:5 char:1 + $Resource.Properties.minimumElasticInstanceCount = 3 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : PropertyNotFound

<!-- end snippet -->

Do you know what could be the problem?

Have you logged in within your runbook?

The first error tells you to connect using Connect-AzAccount and the 2nd error is a generic error that the property doesn't exist because $Resource object doesn't have that property.

1. First error:

In the Automation Account console, under Account Settings -> Identity, be sure to have the System Assigned identity to on:

Then, click in the "Azure role assignments" button and check if you have the "Contributor" role in the resource group of your function app and assigned to the azure automation account:

Finally add this code in your scripts:

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

# Connect to Azure with system-assigned managed identity
$AzureContext = (Connect-AzAccount -Identity).context

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

2. Second error:

Go to the Function App console, then under Settings click on "Configuration" and verify that you have the property "minimumElasticInstanceCount":

If you don't have this property you can simply create it clicking in the "New application setting" button.

This is a useful Azure documentation:

https://learn.microsoft.com/en-us/azure/automation/enable-managed-identity-for-automation#authenticate-access-with-system-assigned-managed-identity

The error "Run Connect-AzAccount to login" indicates that the call to run the command is not made in a security context that is allowed to make the call.

In your case it is the logic app that is making the call. So first thing to check is the security context of your logic app.