Hello Andrii Lytvynenko,
The behavior you're observing appears to be related to timing issues at the start of the billing cycle, during which forecast data may not yet be fully populated when the alert is triggered. As a result, certain fields in the payload—such as ForecastedDate
, ForecastedAmount
, and ForecastedPercentage
—may remain unset or default to placeholder values.
As there is currently no official Microsoft documentation or confirmed workaround addressing this specific issue, I recommend the following steps:
- Monitor the alert behavior over the next few days to determine if the forecast fields populate correctly in subsequent alerts.
- Consider switching to the Common Alert Schema, which may provide more consistent payload formatting and improved support.
- If the issue persists or impacts your automation workflows, I suggest raising a support request with Microsoft Azure for further investigation and visibility. You can create a support request using the following link:https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview
Please let me know if you need any further assistance regarding this issue—I'm here to help.
let us know if any help, we will always help as you needed.!
Please do not forget to "Accept the answer” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.