Configuring Teams calendar access for Exchange on-premises mailboxes
Over the last several months, we have seen many customers adopting Microsoft Teams, even if their mailboxes are still hosted in an on-premises environment. One of the common issues in this scenario is not being able to see the Calendar tab in the Microsoft Teams client.FindTime, your favorite scheduling add-in just got better!
We heard you and so we re-wrote the entire back-end infrastructure for FindTime, we built a new service within the Office 365 compliance boundary! More specifically, the organizer’s poll data is now stored in their mailbox and will not leave your tenant’s environment.Calendaring is Really Hard to Code and That’s Why You Were An Hour Late to that Meeting
Writing code for calendaring features is hard. You finally figure out a good time for your team to meet and then one of the attendees happens to live in a country that decided to implement Daylight Saving Time (DST) and change the local time by an hour. Just in that country. Here's some advice on what to do and how to handle it.Booking Delegation Vs. Classic Delegation
Calendar delegation can be assigned in two different ways, each for a specific scenario. However, any mailbox, usually rooms, can be assigned both and this causes confusion when managing delegation of rooms or resources. What’s the difference and why? Classic Delegation Classic delegation has been around forever and used when a manager wants one or more people to manage their calendar. For example, a CEO wants their assistant(s) to manage the CEO’s calendar. In this case, the CEO using Outlook or OWA would assign the delegates to the calendar. The Tenant/Org admin has no interaction; this is all controlled by the end users. Classic Delegation assignment works by: Adding Editor permission on the calendar to the delegates Granting Send As permissions to the delegates Creating a hidden transport rule which redirects the meetings to the delegates, red box below. All this is done by the client. The Tenant/Org admin has no involvement. Outlook example: OWA Calendar delegation assignment example: In both cases, classic delegation is completely controlled by end users assigned from the clients. Booking or Resource Delegation This feature is designed to allow the Tenant/Org admin to manage all room and/or resource delegation to specific people to manage, no end user configuration involved. The Tenant/Org admin has total control of who the delegates are for all the rooms and resources. The same calendar permissions and Send As is created but there is no hidden rule for booking delegation, the Resource Booking Agent takes care of redirecting the meetings to the assigned booking delegates. The problem? The problem happens when a room has been configured for classic delegation, then the Tenant/Org admin reassigned/modified delegation from the booking delegation portal. The booking delegation assignment is successful but the classic delegation hidden rule still exists, which will fire first and continue to be redirected to the classic delegates overriding the booking delegates. Solution The easiest solution is to simply logon to the room with the classic delegation and deselect the checkbox that redirects calendaring items to the delegate. Both Booking delegation and Classic Delegation use the same folder permissions and Send As rights. Eric HartmannHow to publish Anonymous Calendar Sharing URL in Exchange Online or Exchange 2013
Do your users want to share their calendar with anonymous users? Here's a tip related to sharing your calendar via a web link for anonymous users (users outside of your organization). Users can publish their calendar for anonymous viewers using OWA . Organization administrators can also publish a user's calendar. Here we will share both of those ways. Note: Publishing your calendar for anonymous users allows anyone with the link to the calendar to view it without having to log-on. Publish your calendar using OWA Publishing your calendar: Log on to OWA and go to Calendar. Right click the calendar you want to share and choose permissions: Change the permissions drop-down from “Not Shared” (Default) to “Availability only” (or whichever permission you intend to grant) and press Save: Retrieve the link to share it with users outside of your organization: Right click Calendarpermissions > and then View Calendar. This will bring up a browser window with the sharing link (URL). You can also right click on the View Calendar link and then select Copy Shortcut to get copy the link. You can send the link to users outside your organization to allow them to view your calendar Controlling anonymous calendar sharing in your organization Administrators can control whether users can share their calendar with anonymous users outside the organization. If users try to share the calendar when anonymous calendar sharing is not allowed in their organization, they get an error. Administrators must configure a sharing policy to allow users to share their calendar with all domains. For details, see the following articles: Managing Federated Sharing with the EAC Office 365: Sharing in Exchange Online Exchange 2013 on-premises: Sharing Publish a user's calendar (as an organization administrator): If you're an organization admin, here's how you can publish the calendar of a user or a resource/room using PowerShell. Run Set-MailboxCalendarFolder <Username>:\Calendar -PublishEnabled $true Run Get-MailboxCalendarFolder <Username>:\Calendar |fl or Get-MailboxCalendarFolder <Username>:\calendar |fl publishedcalendarurl. This will output the published calendar html (and ics) urls. Others can use this url to view the publisher’s calendar. Example: PS C:\Windows\system32> set-MailboxCalendarFolder calroom1:\calendar -PublishEnabled:$true PS C:\Windows\system32> Get-MailboxCalendarFolder calroom1:\calendar RunspaceId : 0f40e5da-5712-4043-8bbc-fb11049c0307 Identity : calroom1:\calendar PublishEnabled : True PublishDateRangeFrom : ThreeMonths PublishDateRangeTo : ThreeMonths DetailLevel : AvailabilityOnly SearchableUrlEnabled : False PublishedCalendarUrl : http://outlook.office365.com/owa/calendar/6eba91c3eb20499fabc3d831f38b961b@contoso.com /5c3a873ee338449bb7d39dd2f7280b933185741279014858945/calendar.html PublishedICalUrl : http://outlook.office365.com/owa/calendar/6eba91c3eb20499fabc3d831f38b961b@contoso.com /5c3a873ee338449bb7d39dd2f7280b933185741279014858945/calendar.ics IsValid : True ObjectState : Unchanged For more on other calendar sharing options in Exchange Online, please look at thispage. Sathish Venkat Rangam Updates 4/15/2014: Added se ction about sharing policies.Common mailbox / folder sharing scenarios Guided Walkthroughs now available
Exchange and Outlook have, for years, been great collaboration platforms, where our customers could share information easily with others. One of the things that came to light when a lot of our customers adopted Office 365, is that many often have trouble matching their business needs to actual features in the product (stuff they would see in user interfaces and need to configure). In a purely on-premises world, the internal helpdesk and training can help bridge that gap. For those of our customers that have moved to the Office 365 world (especially smaller organizations), this can be a bit of a challenge. We have worked to understand what most commonly looked for (and not found!) sharing scenarios are, and have leveraged the Guided Walkthrough (GWT) framework to help guide customers to correct features they need to get them enabled, taking into the consideration various clients and editions of service they might have. It is worth mentioning that scenarios and steps listed in these GWT s apply to both Exchange Online and on-premises Exchange Server deployments. Typically, the on-premises workflow is the same as can be found if one chooses the “Enterprise Edition” option in those GWT s. Because many of these scenarios are what end-users can accomplish, I would be interested to hear your feedback whether a purely on-premises version would be useful, seeing that on-premises organizations are likely to have resources such as internal help desks and training. Please elaborate a bit in comments if you can, in case you see the value is separate versions? Here are the new GWTs: Sharing calendar and contacts in Office 365 Setting up a mailbox that multiple users can access and use in Office 365 Sending email from another person's mailbox or from a group in Office 365 Accessing other people’s mailboxes in Office 365 Creating and managing resource mailboxes (conference rooms/equipment) in Office 365 It has become a bit of a tradition to thank people who worked on GWT s when we announce them, so not to disappoint, I’d like to thank: Nagesh Mahadev, Jon Bradley, Charlotte Raymundo, Jon Hoerlein, Kweku Ako-Adjei, Sharon Shen, Chen Jiang as well as Scott Vidican, Adam Dudsic and Victor Zhang (ECO). Hope you find this useful. You can give us feedback on Exchange GWTs by either posting a comment in this post (if it is about the 5 GWT listed above) or emailing ExchGWTfeedback AT microsoft.com if it's about any Exchange GWT s. Nino Bilic
