MicrosoftRapid change is a growing reality in cloud services. In Azure AD alone, we are making hundreds of changes every year including new feature releases, changes to existing features, as well as deprecations and retirements. We’ve heard from our customers that managing these changes is becoming increasingly difficult so, starting today, we are simplifying change management for Azure AD.
If your customers are telling you your change rate is becoming increasingly difficult, why continue with the same path? Arrogance? Delaying a change does not simplify the change.
You, Microsoft, are not making my job easier. In fact, you're making it more difficult. I often feel like it's a one step forward, two steps back type of situation. Sure, some improvements are made that should help me. However, those improvements are then nullified with changes such as the planned deprecation of MSOL, when you don't have full functionality in the planned replacement. How can you expect anything other than criticism from those of us who depend on that which you plan to deprecate when you don't have a viable solution available? Arrogance?
I don't think you understand the constraints many of us have. I don't have staff to try to keep pace with the change rate Microsoft seems to believe is acceptable in what I think is core functionality. If I don't have staff for that, I certainly don't have it to keep checking if you've finally made necessary functionality available in Microsoft Graph PowerShell. So, I'll most likely experience a negative impact once you make it impossible for me to use MSOL.
Your software should make my job easier. Your business practices should do the same.
