Office 365 Group not showing in Outlook (Exchange Hybrid Environment)

PROBLEM:-

I have an issue where a Microsoft 365 group has been created but will not appear in Outlook 2019 or Outlook on the web.

After a bit of digging, I found out that the following factors played a part in this.

  • Exchange is running in Hybrid environment
  • User had created the Group/Team from within MS Teams

Because we were running a hybrid environment and the user had created the Team/Group from within the MS Teams app it doesn’t do as good a job as it would if you created it via the web-based admin interface.

When the group is created from the MS Teams app it doesn’t set the exchange attribute –HiddenFromExchangeClientsEnabled:$false which means that by default the group will not appear in Outlook App or Outlook on the web.

If you create the group via the Microsoft 365 admin center it works fine.

SOLUTION:-

1. Open up Windows Powershell and connect to Exchange online using the following command. (Make sure you have Powershell 7 and the exchange EXO V2 module installed).

connect-ExchangeOnline -UserPrincipalName [email protected]

2. Set the groups visibility using the following command

Set-UnifiedGroup -Identity "Name of Your Group Here" -HiddenFromExchangeClientsEnabled:$false

Install the latest Windows PowerShell and Exchange Online Management EXO V2module

I often find that I’ll jump on to a server, PC or laptop and I’m trying to run commands in PowerShell that it doesn’t understand. Normally because it’s an old version of PowerShell, certain modules aren’t installed or I’m just bad at typing.

Here’s where to get the latest version of Windows PowerShell and EXO V2 that you will need if you’re working with Exchange Online.

PowerShell 7
https://aka.ms/PSWindows

Exchange Online Management
https://www.powershellgallery.com/packages/ExchangeOnlineManagement/

At the time of writing the following command will get you the module…

Install-Module -Name ExchangeOnlineManagement -RequiredVersion 2.0.5

Check what modules are installed…

Get-InstalledModule

Drivers for Digital Persona U.are.U 4500 Fingerprint Reader USB

Below you will find 2 zip files that can be used to get your Digital Persona U.are.U 4500 up and running. The first 4500_wbf_driver_5.0.0.5_rs3.zip is smaller in size and is just the basic drivers, probably all you need to get up and running on Windows 10. The second DP_UareU_WSDK223.zip I believe is the SDK kit and has all the drivers and full software.

 

MFA not working in Outlook 2019 – Exchange Online

Scenario:-

Microsoft 365 tenant, mainly using Exchange Online (Plan 1) licenses. I enabled MFA for a couple of users which works fine logging in to https://office.com

Users can access Outlook on the web without any problems and get notifications sent to the “Microsoft Authenticator” app to approve or SMS if they choose one of the other authentication options.

When it comes to Outlook 2019 they just repeatedly get asked for their email credentials in a standard type popup box as opposed to the newer MFA style popup that you see like when you login to https://office.com where it asks for email, then password, then MFA option.

I know this type of problems exists with older versions of Outlook 2013 and lower and there are workarounds for it but this is Office 2019!

Solution:-

After raising a support ticket with Microsoft and getting a call back pretty much straight away from a very knowledgeable “Support Ambassador” we managed to sort the problem. Turns out that if your tenant was created before 2017 (ours was 2014) then the default policies in place for the basic Azure type licenses that come with the lower tiered licenses like Exchange Online might not work very well when enabling MFA on a user account! Tenants created later than 2017 tend to work just fine.

Here’s what we did…

  1. Run PowerShell as admin
  2. Connect to Exchange Online (If user has MFA enabled) using the following steps:-
    $MFA = New-Object -ComObject InternetExplorer.Application -Property @{Navigate2="https://cmdletpswmodule.blob.core.windows.net/exopsmodule/Microsoft.Online.CSE.PSModule.Client.application"}

    The command above installs a module which then launches another PowerShell window.

  3. In the newly opened window enter the following:-
    Connect-EXOPSSession

    Enter your tenant administrator login information.

  4. Enter the following command:-
    Set-OrganizationConfig -OAuth2ClientProfileEnabled $true 

This pretty much enables the use of MFA now for your Exchange Online tenant. It can take a few hours for things to propagate and for Outlook 2019 to make use of this. If you need to speed this process up you can add the following registry key to the users computer. Make sure to close Outlook first.

  • HKEY_CURRENT_USER\Software\Microsoft\Exchange
  • On the Edit menu, point to New, and then click DWORD Value.
  • Type AlwaysUseMSOAuthForAutoDiscover, and then press Enter.
  • Right-click AlwaysUseMSOAuthForAutoDiscover, and then click Modify.
  • In the Value data box, type 1, and then click OK.
  • Exit Registry Editor.

Open Outlook and you should now get the MFA type prompt as you would expect. I think if you continue to have problems then it’s worth deleting the Outlook profile on the computer and starting again.

The following article may also be of use as it goes into a lot more detail about how to enable or disable modern authentication for Outlook in Exchange Online https://docs.microsoft.com/en-us/Exchange/clients-and-mobile-in-exchange-online/enable-or-disable-modern-authentication-in-exchange-online

One last thing… enabling modern authentication for Outlook in Exchange Online wont affect any of your other users who may not have MFA setup.

Hopefully this may help someone somewhere one day!

Enable or Disable write protection to a USB drive

PROBLEM: I need to stop users saving data to a bitlocker usb flash drive that they use to unlock their laptop.

SOLUTION: Use the DiskPart command line utility to enable read only access to the USB flash drive in question.

STEPS:-

  1. Press the Windows key + R to open the run box.
  2. Type diskpart and press enter.
  3. If you receive a UAC prompt asking for permission click Yes.
  4. At the DISKPART > prompt type list disk and press enter.
  5. Figure out which is your USB disk based on the size (mine was disk 1) so I typed select disk 1 and pressed enter.
  6. You can check the attributes for the disk by typing attributes disk.
  7. To enable disk write protection (making it not possible to save files to the disk) use the command attributes disk set readonly and press enter.
  8. You’re done! Type exit to quit.
  9. If you ever wanted to revert back and disable write protection then use the command attributes disk clear readonly and press enter.

DiskPart

Please note that the above method will only enable write protection for that particular usb flash drive on that specific windows machine. If you were to put the same usb flash drive in a different machine you can still write files to it.

How to add Azure Active Directory user to local administrator group

Windows 10 allows you to join your computer to the Azure Active Directory and login with your cloud credentials. The first account that joins the AAD becomes a local administrator. Subsequent users are not.

To add additional azure accounts as local admins you need to do the following…

  1. Open a command prompt with Administrator proviledges
  2. Enter the following command…
net localgroup administrators /add "AzureAD\<users office 365 email address>"

You should see “The command completed successfully”, now go check it worked by going into computer management > Local Users and Groups > Groups > Administrators and check to see if the user is listed.

Outlook keeps asking for password… Using Office 365 but on-premise exchange?

Starting in Outlook 2016 version 16.0.6741.2017, Microsoft has enabled a new feature called Direct Connect to Office 365. What this feature does is connect Outlook directly to Office 365 if Autodiscover is not working. This is great feature but a network hiccup may cause your mailbox to connect to Office 365 rather than your on premise Exchange, even with a valid autodiscover record.

For Direct Connect to take effect the user must have an active mailbox on Office 365 with a valid license. Typically Direct Connect would be a neat feature unles you are in the middle of a migration to 365, but a network hiccup could incorrectly connect you to 365 even though you havent completed your migration yet.

During 365 migrations deom Hosted Exchange or On-Premise, we recommend disabling this option from the user computer registry:

You can stop Outlook from checking Office 365 for settings by setting a registry key.

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover
DWORD: ExcludeExplicitO365Endpoint
Value = 1

Then restart your computer and it should stop trying to connect to Office 365. When you are ready to flip the switch on your migration, remove this registry key.

Heres a great article describing the whole thing in more detail…
https://www.enowsoftware.com/solutions-engine/autodiscover-dilemma