03-15-2018 07:15 AM
The message was retracted, and the original recommendations stand. However, even though this was retracted, be advised that ultimately Exchange Unified Messaging is a dead product based upon very old technologies and will very likely never see new development or updates. It's not a direction you'd want to head unless you have no other option. I suppose there's a chance that the vendor products that connect with it will be able to leverage Azure VM in future versions, but that's pure speculation on my part at this point.
03-15-2018 07:48 AM
anynode is already able to use Azure VM and Exchange UM. That was the initial approach to use Skype for Business instead of a direct connection in the cloud. Maintain 2 solutions for the same feature does not make any sense.
Depending on the user´s home anynode (the call) will end up in Exchange UM or Azure Voicemail.
We expect more changes in the backend to get a 100% feature parity.
03-16-2018 11:39 AM
any third party recommendation from microsoft. we are looking into the options of AVST and Avaya
03-26-2018 07:11 AM
Thanks Anthony. From what I can tell, Azure VM requires Phone System PBX licensing. It doesn't make sense to license Phone System while simultaneously attaching your users to an external PBX (essentially double-paying), except perhaps in a migration scenario.
I think customers who leverage Exchange UM with a 3rd party PBX are still looking for solution to go to the cloud. I was disappointed to confirm that X-UM requires Enterprise Voice CALs, and am currently trying to find out whether anynode has the same requirement.
04-02-2018 02:49 PM
Anynode will have the same requirement I suspect, it's just the way it's designed to communicate. It's basically an trusted application bolt-on to Skype that delivers direct to voicemail from what I understand.
04-02-2018 03:07 PM
04-03-2018 08:39 AM
I like AVST, I've used them on deployments even in the Lync days when the corporation wasn't fully on Exchange.
07-27-2018 10:19 AM
03-26-2019 11:37 AM
@Steve Conn Sorry to hear that you moved from Exchange Team Manager role.
I just spoke to Nathan Abennet and he explained that this is not an official place to accept the technology solutions. For the years, we learned from many Microsoft employees about their opinion and accepted as an official word but these are just their personal views which can't be taken as official Microsoft statement.
So, the final word from my call is, option 3 is not supported for Message Waiting Indicator and we have to develop EWS for this functionality.
03-26-2019 11:59 AM
@Prabhat Nigam Hi Mr. Nigam - thank you for your kind thoughts. Please note that my original post at the top of this thread was placed here as a courtesy notification. The official notice was via Message Center post, and echoed via the Exchange Team blog. Also note that there has been change in the recommendations, etc. from the time that we did the initial notification, so the post at the top of this thread has been superceded. Thanks! Steve
03-26-2019 02:54 PM
@Steve Conn you are way too polite in response to the rubbish written in the previous response. I admire your restraint.
03-29-2019 11:46 AM
@Steve Conn Thank you for the quick response.
Not sure what makes Tony mad, just my presence or something in my text.
My text was the words from PG (Nathan's) and I am just a messenger who is delivering them to get this technical issue fixed for everyone.