Within documentation or in the product overview pages include a list of other Azure services that are dependencies for Key Vault
When large organizations adopt cloud services they may evaluate the cloud service in depth, along with all other cloud services that must or may be adopted as dependencies of the primary service being planned for use. An example is that when adopting Azure Key Vault a customer will be required to adopt Azure Active Directory if not already adopted, and therefore adopting Key Vault will necessitate an in-depth security assessment of Azure AD in addition to Key Vault.
Currently Microsoft does not list dependencies of any kind on the product web pages of all the many Azure services. This obliges the customer to go on a fact-finding mission to uncover these dependency relationships and therefore costs time on the part of both the customer and Microsoft. This might include account team members, CxE, and product teams. This would be unnecessary if all dependencies (both mandatory and optional) were clearly stated on the product pages of every Microsoft service.