In a multi-tenant environment is there a limit to how many different tenants, independant AAs, schedules, etc that can be configured within Unity?
Thanks in advance. All replies rated.
This would definitely require some serious consideration regarding architecture and capabilities. First take a look here to get an idea of what design guidelines you need to be aware of:
First, you need to consider if Unity will be capable of providing the services that you want given what you have described. Since Unity is tightly integrated into Active Directory and Exchange, you may need to look at having multiple Unity systems that are digitally networked. But, before we go further down the Unity route - definitely take a look at the design guide in general and particularly, the section noted above.
With Unity Connection, the architecture is likely to be much simpler as there is no inherent dependence on AD or Exchange. Granted, you would be providing an Integrated Messaging (IMAP) vs. Unified Messaging experience; however, the complexity would be reduced. Unity Connection doesn't care necessarily care about AD (unless you want to set up LDAP integration) or Exchange (unless you want to set up a external service which provides calendar integration with voicemail). It also provides the ability to build separate partitions and CSS's that would keep each "customer" separate and distinct of one another. You also still have the ability to stand up multiple systems and digitally network to provide greater scalability, as needed.
Please rate helpful posts!