Translated to English:
Hi @清水雄樹 ,
Yes, you would have to make sure the cmdlet's related module is imported in your Azure Automation account.
In general you would receive below mentioned error if the cmdlet's related module is not imported.
System.Management.Automation.CommandNotFoundException: The term 'xxxxxxx' is not recognized as the name of a cmdlet, function, script file, or accurately program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
In your case, I would recommend to successfully import Az.Compute module in your Azure Automation account and then try to execute the runbook.
Follow the steps provided here (https://learn.microsoft.com/azure/automation/shared-resources/modules#import-az-modules) to import a module in an Azure Automation account.
Let me know if you have further questions with regards to it.