Microsoft announce the public preview of Azure Cost Management anomaly detection. This alerts you to inconsistencies in spending across an Azure Subscription to help you to identify unexpected changes in cost.
Find the announcement here: https://bit.ly/3hfOfDL.
There’s an updated (July 2021) Dynamics 365 Licensing Guide with 3 changes of note.
Firstly, Fraud Protection transactions can now be paid for on a consumption basis against an Azure Subscription – find the details on our blog here: https://bit.ly/3i5WCTw.
Secondly, there are some changes to Business Central capacity – find the details on our blog here: https://bit.ly/3i68DbO.
And finally, there’s some clarification added to the definition of the Average Order Value specifying that it’s the Gross Merchandise Value (total value of all transactions processed through Dynamics 365) divided by the total transaction volume.
Find this updated guide here: https://bit.ly/3qIoik1.
Dynamics 365 Fraud Protection customers can now pay for their Fraud Protection transactions on a PAYG basis each month. There are three pricing tiers for each workload with, as you’d expect, prices decreasing as the number of transactions increases. To enable monthly billing, customers need to purchase a monthly Fraud Protection PAYG license for $12 per month, and then choose the Azure Subscription that they want the Fraud Protection transactions billed against.
You can find details of the different pricing tiers and setup instructions here: https://bit.ly/3BCWToL.
If you’ve got a question about how the Azure DevOps Services are billed then this FAQ is worth a read: https://bit.ly/2RvUDKt. There’s also a section on multi-organisation billing which was recently announced here: https://bit.ly/2yNdPwM, and enables businesses with more than one Azure DevOps organisation to pay for each user once for all organisations under the same billing Azure Subscription.