Pool1 is joined to an Azure AD DS managed domain (contoso.com). You will use Azure Automation runbooks to scale Pool1 and need to authorize the runbooks with minimal administrative effort. What should you configure?

A managed identity in Azure AD is the correct choice because it provides an automatically managed identity for Azure resources to authenticate to cloud services without managing credentials. This aligns with the requirement for minimal administrative effort for authorizing runbooks. A gMSA in Azure AD DS is used for services running on Windows Server to authenticate to other services, not for Azure Automation runbooks to authenticate to Azure resources. A Connections shared resource in Azure Automation is a way to store connection information, but it doesn't provide an identity for authentication. A Run As account in Azure Automation is an older method for authentication that uses a service principal and certificate, requiring more administrative overhead than a managed identity.