wooden-lifeguard-41446
12/17/2021, 9:20 AMchecking for presence of existing Automation Account "automationaccountname" (Resource Group "resourcegroupname"): automation.AccountClient#Get: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code="AuthorizationFailed" Message="The client '<mailto:user@email.com|user@email.com>' with object id 'object-id' does not have authorization to perform action 'Microsoft.Automation/automationAccounts/read' over scope '/subscriptions/subid/resourceGroups/rg/providers/Microsoft.Automation/automationAccounts/automationaccountname' or the scope is invalid. If access was recently granted, please refresh your credentials."
I already gave my self every permissions (Owner, Contributor, Runbook Operator). I can create it when using AzureNative Provider.
The reason I don't want to go with AzureNative is that it only allows me to create the runbook content by using Content Link Uri.
I appreciate any help on this!No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.
Powered by