Outlook calendar Service (Ignite 2018 Review). Microsoft held their ignite session and I would talk about some features which will coming soon. This impact clients on Office 365 primarily while it will be pushed down to on-premise deployments as a later stage. I had summarized the important bits for client which I think important to know. A lot of times issues arises and by providing feedback, Microsoft does ensure changes are done.
New features are subscription based. Coming soon icon to turn it and off of new features. Feedback will be great to provide to Microsoft. The “coming soon” feature will be available for the web and also for Mac.
Meeting attendance tracking will now be able to track when the an attendee select “Do not send a response“. This make it easier for the organizer to be aware of who will be attending. You will now be able to track meeting attendees on mobile devices as well. The room will be able to set out a response as well. Attendees will know how many attendees will
be available through a mail tip.
There will now be a tracking pane to manage this separately for the organizer and attendees. Limit of 500 max attendees has been lifted. Tracking responses can now cater for up to 2000. Preventing forwarding of meetings can now be prevented. This feature is to control the amount of small meeting turning out too large.Outlook for Mac will support this in Q4, 2019. When you use Office 365, Exchange 2016 or 2019, the NDR will be done on the transport layer. Forwarding will now be limited to only the organizer.
Free / Busy speed has been increased from 4 seconds to 200 ms. Caching of free / busy are being cached on the local profile and when someone queries the mailbox, it will populate much quicker. Rest of the queries has been optimized to 800 ms.Time zone meeting can set on fly depending if you flying out etc. instead of using your local time zone and adjusting as you reach your destination. This will be available on Windows, Mac and Web. FindTime add-in for poll solution is available. Compliant with GDPR regulations. Browse for resource room capacity filter is coming soon. Room history will be a feature during the search room. It is based booked previously,
mainly attended and then available.
Microsoft teams is available on Office 365. You now will be able to book meeting through Outlook using team meetings. This integrates with Skype for Business. Calendar sharing now has more features coming soon. You will now be able to share across tenants based on tenant settings. New model of sharing creates a local copy of the calendar in the delegate mailboxes. Calendar sync happens on the server
to avoid latency. Mobile apps sees the calendar as another calendar and works better. Read / write sharing across tenant is in development. Delegate calendars which are are now residing in the mailbox, protocol will now be changed from Mapi to REST. Managing REST calendars for Windows, there will be a GPO to configure this. Mac Outlook calendars will be sync over REST as well.
Mac calendar will now support with REST, view shared calendars. Recurring meeting going forward when deleted, will be removed from outlook calendar but the history will remain. Declining calendar meeting will keep a record but will only display on the web. Home time zone will assist when scheduling meeting with users in different time zone and will account for their working hours and free / available to
ensure setup of meeting is made easier. Resizing of attendees name column will be available. Auto-close of complete meeting in the reminder
Moving to REST fixes a lot of general calendar sharing on Mac. Granting permissions was set using the following flags:
Delegates permission can now be set via command-line with the properties of -SharingPermissionFlags Delegate,CanViewPrivateEvents
To view the Microsoft Ignite Calendar service session, see below link:
Microsoft keeps documentation updated with the available permission. You can locate by going to the following link:
For those who are not familiar with REST connection, here is a quick explanation on it.
Representational State Transfer (REST) is an architectural style that defines a set of constraints to be used for creating web services. Web services that conform to the REST architectural style, or RESTful web services, provide interoperability between computer systems on the Internet. REST-compliant web services allow the requesting systems to access and manipulate textual representations of web resources by using a uniform and predefined set of stateless operations. Other kinds of web services, such as SOAP web services, expose their own arbitrary sets of operations. “Web resources” were first defined on the World Wide Web as documents or files identified by their URLs. However, today they have a much more generic and abstract definition that encompasses every thing or entity that can be identified, named, addressed, or handled, in any way whatsoever, on the web. In a RESTful web service, requests made to a resource’s URI will elicit a response with a payload formatted in either HTML, XML, JSON, or some other format. The response can confirm that some alteration has been made to the stored resource, and the response can provide hypertext links to other related resources or collections of resources. When HTTP is used, as is most common, the operations available are GET, POST, PUT, DELETE, and other predefined CRUD HTTP methods.
By using a stateless protocol and standard operations, REST systems aim for fast performance, reliability, and the ability to grow, by re-using components that can be managed and updated without affecting the system as a whole, even while it is running. The term representational state transfer was introduced and defined in 2000 by Roy Fielding in his doctoral dissertation.Fielding’s dissertation explained the REST principles that were known as the “HTTP object model” beginning in 1994, and were used in designing the HTTP 1.1 and Uniform Resource Identifiers (URI) standards. The term is intended to evoke an image of how a well-designed Web application behaves: it is a network of Web resources (a virtual state-machine) where the user progresses through the application by selecting links, such as
/user/tom, and operations such as GET or DELETE (state transitions), resulting in the next resource (representing the next state of the application) being transferred to the user for their use.
To know more about how the protocol work, you may go to the following : REST