![skype for business user guide 2017 skype for business user guide 2017](https://s3.manualzz.com/store/data/032002131_1-dd91bf6e0dbbd9412858b82527f14dd5-360x466.png)
![skype for business user guide 2017 skype for business user guide 2017](https://www.pei.com/wp-content/uploads/2017/11/Outlook-Meeting-Polls-610x365.png)
Now, for the first time you can have a fully cloud-hosted end-to-end customer service / remote advisor / B2C scenario using native Skype for Business technology. We need to work on naming, but with the release of the Trusted Application API (Dynamic Guest Access) – TAA(DGA) – Tagda? – we can start to see the long-term vision the Skype for Business Platform Team have had becoming a reality.
![skype for business user guide 2017 skype for business user guide 2017](https://jamesosw.files.wordpress.com/2017/09/not_appearing_02.png)
In fact, that’s exactly the scenario offered by the health care templates! That also means you have (just) enough features to create a fully functional Business-to-Consumer (B2C) scenario where the business sets up a secure meeting area (a Skype for Business conference), brings in people from the business (maybe who use the Skype for Business client), then exposes a secure link to a customer to allow them to join the meeting anonymously, either over the web or using a mobile application (courtesy of the Skype for Business App SDK). That’s all new capability we didn’t have before this announcement. If you’re thinking “is that it?”, well – you need to take into account as well that these two features are offered as a REST-based API which can run as a web service in Azure (or any other Cloud) and can talk to Skype for Business Online. So, what actually is Dynamic Guest Access? It’s essentially two Skype for Business features: scheduling a meeting, and authorising guest users securely allowing them to anonymously join the meeting. It’s my guess that they identified what functionality they would need to deliver a really compelling set of healthcare templates and targeted those features in the API first, hence leading to the Public Preview of Dynamic Guest Access. Microsoft have a focus on healthcare that extends way beyond Skype for Business so this is clearly an important area for them. This agile method of delivery certainly gets my vote because it means we can all start using the most requested features sooner. It seems that we’re now starting to see the fruits of all the effort that started even before MS Ignite 2016 and have been continuing over the winter months.īringing us up to date, what I think we’re seeing is that rather than releasing an entire API, 100% complete, delivered as a fait accompli with a bow on, the Platform Team are instead choosing to focus on the most useful, most demanded functionality first and releasing it as soon as it’s ready, before concentrating on the next most important feature, and so on. In fact, there was even a timeline slide: At that time we were told it would be coming to Skype for Business Online first, with on-premises solutions being offered later. I wrote about it then and there are some good slides and detail about the problems it solves. In October 2016, as MS Ignite, Microsoft first publicly mentioned the Trusted Application API. But, it’s only the Dynamic Guest Access part of the Trusted Application API which is being made Public Preview.Ĭlear? OK, let’s dig into it in a bit more detail. And that functionality is offered as part of the Trusted Application API. That functionality is called Dynamic Guest Access. It’s that technology which is moving into Public Preview today. What was interesting about those templates was that the functionality they describe couldn’t be achieved without some extra technology not previously available. Last week, Microsoft released a new set of templates aimed at the healthcare market. You can read the announcement here, but be warned that it doesn’t actually mention “Trusted Application API” anywhere. Microsoft folk: if you would like to clarify/correct any of this, please reach out on the usual channels. I don’t have all the answers back yet so this information might change, but this is what I know today. I’ve also asked around some folks at Microsoft for clarification. It’s been a few days, and I’ve sat on my hands because I wanted to completely understand everything before I wrote it here, and I wanted to make sure I wasn’t breaching any NDAs. I think I’ve got it and I think I understand what’s going on.