Azure AD B2C is great and the pricing too, except for the fact, that token refreshs carried out by the application (as opposed to being carried out by the user) are charged separately. An application that keeps a logical connection to the server while in the background, might carry out quite many token refreshs over time. A regular frequency of one refresh per hour leads to ~700 refreshs per month. Assuming 1.000.000 users, this sums up to ~500.000$/month. This exceeds the capacity of start-ups like ours by a factor of 1000 (!). Although AD B2C would be the perfect fit for our business, this kind of pricing prevents us from using it.

Suggestion: Charge for authentications initiated by the user but don't charge for token refresh initiated by the application.

CSP is a great purchasing model for small and medium businesses, but has some serious problems.

1) Migrating between CSP and any other offer is a very laboursome and expensive project (not to mention that many resources cannot be migrated). This can cause Vendor lock-in and some other major risks for customers using CSP. Currently even PAYG to CSP is not easy.

2) CSP customers are unequal to other Azure users despite the fact that they pay the same or sometimes even more, because they do not have the same services available to them.

3) CSP resellers have to put in a lot of labour to onboard existing customers.

Please work on harmonizing the services between the different offer types so that a Customer in CSP is equal in terms of what services they can use. Furthermore, work on enabling (MS Support assisted or self-service) migration from CSP to PAYG/EA AND vice versa ON THE BILLING LEVEL without service interruptions (as with PAYG to EA or EA to PAYG).

In the MFA release plan of a large company, thousands users are impossible to actually "force" from the day.

So, the user needs a period which setting for the MFA can be skipped, before force setting period.

In the period, it provide a selection such as "set up later" in the MFA setting wizard at the initial sign-in.

if someone did not have a mobile device on that day,
if someone wants to ask questions about MFA, etc...
they can not access any Office 365.
becouse, even if you set a policy to skip MFA on the LAN, the MFA Setup Wizard will be forced.
As a result, Organization is subjected to a large negative impact!

Azure is prohibitively expensive for small businesses and new/poor developers.

£150 for 30 days is not long enough to get up and running and to make a viable website/app to cover the costs.

Suggestions:
-Allow users to use the free credits over 12 or 6 or even 3 months.
-Or return to your previous offer with free monthly credits for a year.
-Or offer SSL on the shared plan. (sites without SSL are not an option)

£50-£60/pm for a basic website with custom domain and SSL is ridiculous.

I feel my only option is to abandon Azure and look at something like Google's GCP (who are offering $300 for a year), which means I have wasted many years learning the Microsoft and Azure stack.

I really hope you can review your current offers and make Azure a better choice.

Thanks

Azure has many options so that trying out and learning how to work different scenarios is quite involved. There is a lot to learn and one month is not enough, especially as it is unlikely that someone can dedicate a full time month to Azure. Personally, I can't be bothered to try Azure for just 30 days - what's the point? It took me several months of occasional sessions to get the full hang of AWS. I am sure Azure is the greatest thing since sliced bread, but for the time being, I will stick with what works for me, i.e. AWS.