Microsoft AZ-305

Azure Log Analytics is the correct choice because it can ingest Azure Activity Log data (control-plane events) into a Log Analytics workspace and enable KQL queries to identify new ARM deployments over a monthly window. You can then automate monthly reporting using scheduled query rules and export/notify mechanisms. This is the standard Azure Monitor approach for centralized auditing and reporting across a subscription.

Azure Arc is primarily used to project non-Azure servers, Kubernetes clusters, and some data services into Azure for unified management and governance. It is not designed to collect and report on ARM deployment events within an Azure subscription. While Arc can integrate with Azure Monitor for Arc-enabled resources, it doesn’t replace Activity Log + Log Analytics for deployment reporting.

Azure Analysis Services provides a semantic modeling layer (tabular models) for business intelligence scenarios, typically consumed by Power BI. It does not natively collect Azure Activity Log or ARM deployment operations. You could theoretically build a model on top of exported logs, but it’s not the appropriate or direct service for generating a monthly report of new ARM deployments.

Azure Monitor action groups define the notification and automation targets (email, SMS, webhook, Logic App, Function, ITSM, etc.) used by alerts. They do not store or query deployment data. Action groups can be used to deliver a report or alert triggered by a Log Analytics scheduled query, but they are not sufficient by themselves to generate the monthly deployment report.