O365 Group created from Teams don’t show up in Outlook desktop and online

Up until a few months ago, when I created a new Microsoft Teams team, it would also show me a mailbox and calendar for the underlying O365 group in Outlook 2016/2019 and OWA.  I then spent a lot of time baffled and trying to figure out what changed.

Finally I found the answer on a Tony Redmond post.  Clutch as usual, thx Tony!  The short answer was that Exchange Online has an O365 Groups setting called “HiddenFromExchangeClientsEnabled” that was used to be defaulted to false, but Microsoft changed it to default to true.

I get the rational…for most non-Exchange O365 services (Teams/Planner/others) default implementations/use cases (where there is no implemented governance controls on who can create a team/plan/etc.), users may not want/need or even understand that there is a mailbox tied to their new group when they create the team.  The problem is that there are many use cases where access to the mailbox was intended/needed.

The only current solution I found so far to this issue is to create the O365 group in Exchange/Outlook first and then when creating the Teams’ team, use the existing O365 group.  This however is a bit of a hassle and not at all practical in any organization where you want to allow users (non-IT staff) to create teams.

Others have proposed that Microsoft should allow the option to show the mailbox when creating the team in Teams (see User Voice post).  I agree with this, but also wanted to find a way to add this option as part of an automated controlled Teams creation/governance process.  Unfortunately other than using the Exchange PowerShell module, I haven’t found an API solution yet (including Graph/AzureADPreview).  If someone knows of or finds one, please hit me up!!!

If you are running into this issue as well and you want to use the Exchance PowerShell module for now, I found a few articles on the interweb, but Tony Redmond’s is the best explanation and Morgan TechSpace has the most concise directions.  Cheers.


Microsoft Teams / Skype for Business coexistence and interoperability

For some time now Microsoft has made no bones about the fact that Microsoft Teams is the future replacement for Skype for Business (S4B).  In fact there isn’t much you can do in S4B that isn’t already in Teams today.

By default, you have S4B and Teams side by side and most organizations don’t change this at the onset.  Fortunately Microsoft has now published an article to Understand Microsoft Teams and Skype for Business coexistence and interoperability that can explain all the options on how this can work.  Note that best practices recommend a controlled rollout of Microsoft Teams, once a usage guidelines and governance strategy has been defined for the organization.

The issue that most organizations have is how to migrate their users over to Teams.  The default situation means that most users will continue to use S4B until they find the people they want to communicate with are already communicating on Teams.  At that point they will use both until all the people they communicate with are migrated.

This is generally okay as most organizations want some pilot or leading edge users to try it out before migrating everyone.  The trick here is that you may want to control who has access to Teams until you are confident or comfortable enough to migrate everyone.  This means a controlled rollout of Microsoft Teams, a topic intimately tied to how you manage Office 365 Groups and has been discussed and documented well in the last year.  Once the pilot is complete, then you can formalize a migration plan consistent with the usage guidelines and governance strategy.

Privileged Access Management (PAM)

Microsoft has for some time now been on a path of improving the privileged access in O365.  Recently they introduced PAM, which is an O365 feature that allows you to add an approval workflow on top of your RBAC controls for various Office 365 admin tasks.

I found a great article called explaining Privileged Access Management in Office 365 very well.  I then found another great article that walks you through implementing it called Exchange Online Introduces Office 365 Privileged Access Management.


External Users trying to accept the invitation get an error message “That Didn’t Work”

There are many reasons why O365 external invitations could fail, but most are obvious reasons…expiry, using non-Microsoft registered emails, etc.

However there is a scenario where the sender and receiver both have done everything right and security settings are set correctly and yet invitation fails.

If this happened to me, I would loose my mind trying to figure out what the problem is!!!

Fortunately someone else has run into this problem and took the time to document the issue and possible resolutions…

QnA Maker

Bots and AI are all the rage these days as the next technologies promising to improve productivity, build efficiencies and capabilities that don’t exist today, change how humans engage with technology, and change the world.

You can see these technologies in play today in Alexa, Google Home, Siri, and Cortana.  These technologies have been integrated into laptops, tablets, and phones.  These same technologies have also spawned whole new families of consumer devices such as the Amazon Echo and other personal assistant devices.  These Bots and AI will eventually be deeply integrated in every device, application, and service.

The most basic and common use of bots has been developing Question and Answer solutions, such as Knowledge Base information and FAQs.  You often see this in adds for the new class of personal assistant devices…”Alexa, what’s the weather tomorrow?”, “Google, who won the Super Bowl?”, “Siri, how far is the north pole?”.  In these cases, the knowledge bases are Search Engine results, which are queried, indexed based on relevance, and read/written back to the user.

The thing about bots is that they can outperform a search engine. Search engines don’t generally give you answers to questions. They give you the source of the answer to your question. You still have to read through the sources to find the answer.  A bot, on the other hand, can actually answer the question directly, providing a link to the source for reference.

As for Office 365 and other Microsoft applications and services, they released the Bot Framework for developers to integrate into their applications.  The first service that Microsoft natively integrated bots into was Microsoft Teams (using a variation of the Bot Framework). Rest assured that it wouldn’t be long before they are integrated into all of Office 365 and other Microsoft products (including SharePoint on premises) for basic application and service based questions.

What’s most important to businesses (i.e. Office 365 customers) however is that bots will allow employees to add frequently used, business relevant and critical knowledge bases to Office 365 (including Teams, SharePoint, Outlook, etc.).  This can all but solve the age-old findability problems for most of their business-critical content, resources, and other assets without employees taking the time to search and identifying relevant results.  This is a game changer for most businesses as they can see huge productivity gains!

Up to now, implementing the Bot Framework or bots into Office 365 requires a developer to implement a bot.  This is why most organizational bot development examples thus far have been FAQs.  Although developing bots allow for big capabilities and potential for business beyond Question and Answer problem, it is a too common use case to need development efforts at each organization.  Microsoft has recognized that re-inventing the wheel here for every organization isn’t wise and has come out with the “QnA Maker” (in preview) to address this common need.  It also allows organizations to start building bots without needing development projects.

With the QnA Maker, the time-consuming part is populating the list of questions and answers to start. Once it’s set up, it’ll be smooth sailing. And you’ll save massive amounts of combined searching time within your organization.

QnA Maker

I first learned about the ‘QnA Maker’ from the good people at BIZZY.  They have SPFx solutions to integrate bots into SharePoint Online, take a look…

Starting Microsoft Teams conversation on items from SharePoint list

For as long as I remember, users have been asking for the ability to have conversations on SharePoint list items and documents.

And for years we have had not so good hacks to get this to work…Wiki Pages, Appending Comment Fields, Lookup Lists, SharePoint Newsfeed, Yammer, 3rd Party tools and Apps, and a ton of other kludgy solutions.

Finally Microsoft Teams comes to the scene and all of a sudden, you can have a conversation and tag a document from SharePoint or even embed the document in a conversation…Hallelujah!

But wait…What about SharePoint list items???

Well we still don’t have a simple coherent out of the box solution just yet.  However it looks like Microsoft didn’t ignore the problem.  It’ll take a little work, but a coherent solution is now here…

Starting Microsoft Teams conversation on items from SharePoint list