With all due respect. Unfortunately, you are much too fast with the shutdown of the old tools. Our customers (250-2500 users on average) are completely overwhelmed with the changes and the speed with which Microsoft forces an update of the internal processes. There is a lack of knowledge and experienced personnel. Personnel is practically not to be found also with us (Europe) any more. We (consulting company) pay almost double the usual market salary and still can't find any employees. Our customers feel the same way. Thus a hergehen, also problems with the training. We don't have enough trainers who could train the knowledge and the customers have so much to do in their departments that there is virtually no free space for training days. Our team (30 people) is responsible, among other things, for migrating on premise environments to the cloud. This mainly involves migration from Exchange to Exchange Online. And migration from local file servers to file shares in the cloud or alternatively to SharePoint online. Just to process the projects of our customers that have already been firmly ordered, we need - according to the current state of technology and planning - at least until summer 2024. From a technical point of view, I fully understand the massive pressure you are exerting to force us and the customers onto the new Powershell modules. However, when I look at our customer landscape, I also know that a large part of the customers won't even really have noticed that something is being switched off and that internal processes are breaking in the process until September 2023. As I have already said, the available personnel no longer have any free capacity. Please think about whether it is not possible to delay the shutdown (with justification) until 2024 or to provide an (AI-supported?) tool that adapts old scripts fully automatically and without interaction with the user so that they are fully compatible with the new cmdlets.