As per tradition, Tony Redmond and I got together at Microsoft Ignite 2018 in Orlando to record a new episode of “Office 365 Exposed” podcast. The Ignite organizers make studios available for this purpose, which is most appreciated. We were joined by special guest and noted humorist Greg Taylor, recently-appointed Microsoft Director of Marketing for Exchange and Exchange Online, to discuss the conference, some announcements made at the event, what Exchange 2019 means for on-premises customers, and what’s happening with Microsoft 365. It’s an easy 45-minute listen.
Tag Archives: Office 365
Sorry that my first blog post in a while is a complaint, but, hey, at least you’re not paying a subscription fee for it.
We ran into an odd problem with our work Microsoft Teams environment. (I’ll blog more about the details once I confirm that it’s fixed; we’re still troubleshooting it.) Thanks to valiant efforts by Tony Redmond and the Teams engineering team, the root cause was tentatively identified as one of the Teams microservices being disabled. I needed to re-enable it.
First stop, the “Enterprise Applications” blade of the Azure portal. Note the list below is the default view, and it’s all you get– a naive user might assume that the list shows all applications in the AAD tenant because the filters are set to “application status any” and “application visibility any,” and the list appears to go from A through W.
But noooooo. Notice that there’s no entry for “Microsoft Teams,” which I know perfectly well is enabled. OK then, let’s try setting the “Show” pulldown to “Microsoft applications.” Set that filter, click “Apply,” and check out the results.
Huh. Still no entry for Teams. This time I notice the text in the search field: “First 20 shown, to search all your applications, enter a display name or the application ID.” All right, fine, I’ll try searching for “Teams”. Type that in, hit return, and…
Well, that seems wrong. Let me try “Microsoft”. That produced a good-sized list of results, very few of which showed up in any of the preceding screenshots.. but only one entry showed up with a name of “Microsoft Teams.”
Finally, Vasil Michev took pity on me and told me to search for “Microsoft Teams.” Et voilà…
There’s the problem child. A couple of clicks later, the service was enabled as intended.
Now, sure, in the grand scheme of things this is a minor issue. There’s so much stuff in the Azure portal, and so many great Azure services, that I can understand that maybe search in this one little corner of the portal isn’t a priority.
Having said that: this is an embarrassing thing to get wrong, and it’s emblematic of similar problems across other Microsoft properties (let’s not even talk about how bad content search is in the Teams client, or why I can’t search Exchange Online archive mailboxes on the Mac Outlook client).
Seriously– fix it, Microsoft.
This episode was recorded at the Continental Hotel in Budapest, where Tony and I were joined by Office 365 MVPs Alan Byrne and Vasil Michev. We explore the wonders of the Spectre/Meltdown vulnerability and learn how it affects– or doesn’t affect– Exchange and Office 365 administrators– and we finally have a name for our “point/counterpoint” segment. Tune in to find out what it is.
Tony and I decided to do a special holiday edition of the podcast to celebrate a banner 2017. In 2018, we have some big things planned– but until then, enjoy this episode where you can learn what our favorite new Office 365 features were, hear Tony fulminate about the Teams PowerShell extension, and find out whether we actually believe that Teams will kill off email (spoiler: nope.)
“Hey, look! A new Office 365 feature!”
I get to say this a lot given how often Microsoft drops new features into various parts of the service. Sometimes they announce these features in advance, and sometimes they don’t. Sometimes these features are large, and sometimes they’re small.. but even the small ones are often surprisingly valuable.
Today’s example: the new Remove-CalendarEvents cmdlet, which solves the issue of what to do with recurring meetings when a user leaves or is on extended leave. Here’s what the documentation says:
This cmdlet cancels meetings in the specified mailbox where the mailbox is the meeting organizer, and the meeting has one or more attendees or resources. It doesn’t cancel appointments or meetings without attendees or resources.
This is perfect for handling the case when someone leaves an organization and leaves behind recurring meetings, but it’s also useful for cleaning up calendar items for people who are on parental leave, medical leave, or other types of absence with a defined start and end time.
You can cancel all meetings with the -CancelOrganizedMeetings switch, or you can specify a date range with switches to specify the start date and the number of days or the end date to cancel. Keep in mind that if you don’t include -CancelOrganizedMeetings, nothing will happen when you run the cmdlet– if you want to see what it would do, you can use -PreviewOnly. I am not sure why the team didn’t use the standard -WhatIf switch, but that’s a minor point.
The cmdlet is very easy to use. I wanted to cancel all future meetings organized by a user who’s left my tenant, so this is what I did:
Note what happened on the first try– I didn’t specify any switches, and the cmdlet warned me that it wouldn’t do anything… and indeed, it didn’t. The second attempt did exactly what it was supposed to:
I was delighted to see this result– it’s proof that Microsoft is paying attention to the small sharp edges that sometimes annoy administrators disproportionately. Hats off to the calendaring team (hi, Julia!) and thanks for listening.
I recently ran into a bizarre problem with the Office 365 Hybrid Configuration Wizard, and solved it after a bit of trial and error. Hopefully this article will be a useful breadcrumb for future hybridizers.
The HCW used to be a standalone Windows executable that you’d download. The Office 365 team (hi, Tim Heeney!) made the wise decision to turn it into a Click-To-Run (C2R) executable. The biggest benefit to using C2R is that whenever you click the link (which downloads the application’s manifest file) you get the latest version of the HCW, streamed directly to you from Microsoft’s servers. This ensures that everyone always gets the most up-to-date version, but it also introduces a few potential stumbling blocks.
C2R application manifests aren’t executable themselves; they’re just XML files that provide some metadata about the application. With that said, on a properly configured Windows box, as soon as you download the manifest, the C2R helper application does its thing; it reads the manifest, streams the application, and launches it.
In my Exchange 2016 lab, that’s not what was happening. When I clicked on the HCW link in Internet Explorer, the little “Scanning..” infobar would flash across the bottom of the window, but that was it. Same thing in Chrome. Downloading the HCW manually using the Start-BitsTransfer PowerShell cmdlet got me the manifest file, but it couldn’t be launched. Of course, since the C2R launcher itself wasn’t launching, there were no log files to use to troubleshoot the problem. By contrast, when I downloaded the HCW onto my Windows 10 desktop, it would fail because I didn’t have the right prerequisites installed, leaving me a log file full of juicy details. All of the machines in my lab had the same problem, perhaps not surprising since they were built from the same Amazon Web Services AMI.
I spent some time doing the usual things: trolling the TechNet forums, searching random posts by people who had problems with the HCW (all of which were problems with what it did after launch, not problems getting it launched), and asking my smart MVP friends. Nada.
Then I had a hunch and opened the Default Programs control panel. For the “.application” file type, this is what I saw:
I changed the “.application” file type to be opened with Internet Explorer. Then I went back to the HCW link, clicked it, and was rewarded with a properly functioning copy of the HCW. Filed for future reference…
I’m delighted to announce that I’ll be presenting 3 sessions at the new Office 365 Engage conference, 19-22 June in Haarlem, The Netherlands.
With the death of TechEd and the product-specific conferences, Microsoft has more or less abandoned the broad conference market in Europe. They’ve hosted smaller, more focused events covering specific technologies in individual countries, but customers who want a broader perspective, or any degree of engagement with non-Microsoft speakers and experts, have had to come to the US-based conferences. Now the UnityConnect team, led by the redoubtable Tony Redmond, are hosting a full-spectrum event focused on all aspects of Office 365, including Teams, Planner, and Groups– not just the more established Exchange/SharePoint/Skype trinity (although there is plenty of that content, too). The speaker lineup is stellar as well; in fact, I wonder how I got in. Attendees will have the opportunity to hear from Michael Van
Hybrid Horenbeeck, Steve Goodman, Michel de Rooij, Sigi Jagott, Brian Reid, Alan Byrne, and a host of other MVPs and Microsoft technology experts. The session catalog is pretty impressive.
As for me, I’m presenting three sessions:
- The Ins and Outs of Monitoring Office 365 covers the fundamentals of monitoring such a complex service environment. Although it may be tempting to just say “let Microsoft worry about it,” the fact is that it’s critical to keep tabs on the health and integrity of the service and all its components, as your users depend on it and probably won’t accept “it was Microsoft’s fault” as an answer. The session will cover the basic tools that Microsoft provides and analyze how they compare to the monitoring needs imposed by dependence on a hybrid cloud service.
- Windows Information Protection and Azure Rights Managment: Better Together. Normally I hate the phrase “better together” because it is Microsoft-speak for “buy more of our products,” but in this case it’s apropos. WIP and AzureRM work quite well together, and the combination enables some interesting data protection scenarios that I’ll cover here in depth.
- Like a Megaphone: Skype Meeting Broadcast will cover the little-known, but quite useful, Skype Meeting Broadcast feature. As its name implies, Broadcast lets you take an ordinary Skype for Business meeting and scale it out to up to 10,000 attendees… but there are some caveats you’ll need to know about to use it effectively.
There’s a full slate of pre-conference workshops, receptions, and so on as well. Perhaps I can persuade Tony to do a live episode of Office 365 Exposed while we’re there– we shall see. Come join me! The conference team has given me a discount code, SPRPR469, which will save you 10% on the registration cost. I hope to see you there!