Top 7 challenges of SAM in the cloud
Challenge #1: licenses are user-based
Licenses in the cloud are generally user-based. That sounds simple, but it also leads to misunderstandings. For example, if five people use one mailbox, an organization has to purchase five licenses, and not one (which is often the case). On the other hand, many other organizations assign a license to a shared mailbox, while that is not necessary (if the users also have their own mailbox and are thus already licensed).
Challenge #2: too many licenses
While organizations on-premise often do not have enough licenses, they can easily have too many in the cloud. Poor management of employees leaving the company, for example, is part of this. Additional licenses are ordered for new employees, but when an employee leaves the organization, their account remains active and the license is not assigned to someone else. This remains a continuing expense: in the case of an on-premise environment, you can look back 90 days and no longer have to license such accounts, but that is not the case in the cloud. In this case, the expenses continue. Organizations also often leave several licenses ‘on the shelf’, so that they can take quick action when new ones are needed (most often because the HR process is not in order). This is also a waste of money.
Challenge #3: not working in the cloud
Cloud license models are often purchased but not used. The installation media used still have to be licensed with the old on-premise licenses and new client software has to be rolled out to be able to apply the new licenses. The organization is not yet ready, or company applications are not compatible with the new cloud software. The transition ends up somewhere on the roadmap and until you actually transition to using the new software, you will remain incompliant and essentially have nothing solved.
Challenge #4: licensing is not always user-based
Cloud licenses are generally user licenses, but that does not apply to certain software. For example, in the case of Advanced Threat Protection for e-mail, the number of licenses must be equal to the number of mailboxes you have. That usually amounts to more than the number of users, due to the additional shared resource mailboxes.
Challenge #5: insufficient knowledge of licensing in Azure
If you take your own licenses to Azure and your organization has an on-premise sub-license, you will take that problem to the cloud as well. Azure does not check that; you will have to do your own license management in Azure as well. Plus: did you know that in Azure, the licenses that are brought in always have to be purchased with maintenance (SA)? And that licenses for some products (desktop applications) cannot even be brought into Azure (or any shared hardware environment)?
Challenge #6: project servers are not switched off
Not every organization switches off the Azure virtual machines (VMs) that are used for a project after the project is completed. That can be a challenge on-premise, but in the cloud, the user costs continue. Better management, proper knowledge of your own environment and correctly structured SAM processes are important here as well. Tooling can provide support in that area.
Challenge #7: hybrid environments make overview difficult
In hybrid environments, it can be extra difficult to get an overview of what is actually used and which licenses are needed. There is often confusion, e.g. on what products are licensed from the cloud and for which installations your own licenses are to be brought in. However, it is also not always clear which licenses you need to be able to use certain software both on-premise and in the cloud.