Havingan issue where user of WVD Windows 10 Multi-session have issues moving between hosts. Essentially first login on a host is fine, when the user moves to a new host outlook eventually says "need password" however the modern authentication prompts are never presented to the user.
Is there a problem with permissions in the credential manager? Because it contains a lot of entries for ADAL, almost seems like it cannot update the 1 existing entry and goes haywire after x amount of time.
we also get this issue by disabling modern auth it stops users outlooks from disconnecting every hour or so however when there password expires thats when it really becomes an issue. Due to our users making use of SharePoint and Onedrive we are unable to make use of the basic auth functions due to modern authentication being required to access these services. I can get it to open a new window if i put in something similar like a .
onmicrosoft.com and then change the address after however this doesnt always work.
The issue that we see is that when a users password expires or they need to authenticate to outlook they would put their email address in or they would click on enter password and the popup would appear and then immediately disappear.
1. ensure devices are appearing as azure hybrid devices in azure active directory (365 side) the devices need to appear as hybrid devices if you are using standard ADDS join and not Azure ADDS. This is due to the fact that users upon sign in need to update device registration when they go to sign into 365 services.
once the above are configured my issues simply went away as much as i tried to break it i couldn't do so. The pre req's on the what is windows virtual desktop is not clear which is why i didn't set the devices up as hybrid devices.
we have currently setup 2 DC's in the Azure Datacenters we operate out off. one of which has AD connect. we also have however on premise DCs with one of those with AD connect. One of the Azure DC's is the PDC now which has AD connect running on it.
It shouldn't matter however where you have AD connect running from as long as it has line of sight of the domain controllers to be able to read and sync the relevant changes to and from ADDS to Azure ADDS.
I would it expect that the ADDBrokerPlugin isn't installed, if so, try to manually register the app:
Add-AppxPackage -Register "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode
Appreciate you may have looked at this already, but I had exactly the same issue - Outlook password box not surfacing correctly to the user in a WVD Win10 session with FSLogix configured. User's shouldn't have been challenged for a password at all.
For me, the issue was that the WVD session host OU was excluded from synchronisation in the AD Connect console. As soon as I enabled synchronisation for the OU, the problem went away. Transparent sign in, no password prompts.
@Tom_A_MSFT
The command to register the AAD Broker plugin works but does not persist after logoff/logon. Additionally, all new profiles need this command to be ran. We have implemented a login script that runs the AAD Broker plugin registration command which is keeping Modern Auth working for all users at this point but we cannot seem to get to the root cause. We have engaged Microsoft support and our partner resources but the issue doesn't seem to be able to be replicated with a standard gallery image.
I'm suspicious of FSLogix. I'm going to test disabling FS Logix and see if local profiles do not have the issue. However, we've simply set everything up per MS documentation on our Win 10 multi-session image, installed Office in shared activation mode per the WVD documentation, then snapshot, sysprep, and re-deployed using the WVD deployment template and our custom/sysprep image. We've also gone back to the bare basics in terms of the FS Logix GPO after tinkering with various settings.
I will update this thread as we learn more but any new information would certainly be appreciated. I'll just state the obvious here but turning off modern authentication through the registry is not an option for our MFA enabled accounts.
I've also found a past issue where FSLogix was having issues with edge and the solution was to register the appx package for edge.
Article on FSLogix forum here:
-US/d18184fe-a703-44e8-a4d3-f824ed10eeb6/ed...
I'm not sure if anyone else has noticed additional appx package issues. We also see a black screen at login for users due to app readiness service. We are also seeing failures for some of these additional appx packages (which can be temporarily fixed by registering again in PowerShell).
Faulting application path:
Click Sign Out under user information. Now, you'll notice that clicking 'sign in' will not work with the current user information, it will just keep failing. Log in with another account (an administrator account or whatver you'd like). It will go through the process of signing in, but will eventually popup an error message as you cannot have two different accounts signed in. Close that error window...but, low and behold, it will ask you to sign into office again. At this point, put the normal user's email and password in again and it will prompt to manage this device/etc. Click through all of those screens and let it do it's thing and you should be good.
I can easily reproduce the issue when using the FSLogix profile service and logging in to the brokered WVD service with the Remote Desktop app, but if I login to the WVD hosts directly using MSTSC, and get a local profile, the issue cannot be reproduced.
We rebuilt the entire host pool using a method given to us directly from a WVD Architect. We configured a new profile UNC path and the issue is back 3-4 days later. We went from 60+ registered Appx packages to maybe a dozen or more. The strange thing now is that the Azure AD Broker plugin is registered but we're seeing the following Azure AD Broker error in the event viewer (see screenshot):
Any email apps you have setup will need to be configured with this login id and password, this includes mobile and desktop clients (MS Mail, MS Outlook). Visit O365/MFA Implementation FAQ for more information on how to set up your device.
I have the Asana Add-in for Outlook Online/Web version. The icon shows up for me to add tasks, but I am unable to login to the add-in when prompted in Safari. I am already logged in to Asana in Safari, but when I try to log-in to the Add-In in outlook a pop-up page shows, asks me to log-in, then closes and I am not logged in.
Hi, anytime we enable "web security" as recommended on the main dashboard of prisma access, MS Teams and outlook stop working. Outlook throws up certificate errors and teams refuses to connect. Upon investigation it looks as though the traffic is being decrypted and this is causing issues. We have put in bypass decryptions for the "worldwide 365 URL" and "worldwide 365 IP" lists in our network security decryption policy. However the logs clearly show this traffic is still being decrypted and breaking the application. It appears that the "web security" feature / policy later is overriding anything set at the network security layer with regards to encryption.
As of February 1, 2023, new student email accounts are provided through Microsoft Office365. Students admitted prior to February 1, 2023, continue to have email accounts through Google (Gmail). Depending on when your email account was created, you may have a Google email account or an Office365 email account. Learn more about each service below.
When you are admitted as a new student and create a MIDAS account, your student email account is automatically activated. This email -- the official system for all University-related communications, policies, announcements, tuition bills and other information -- is yours for as long as you remain a student and is deleted one year after your last class at ODU, whether you graduate, transfer or decide not to register for additional classes.
ODU student email accounts are for active ODU students. If you have not registered for a class in 3 semesters, you will receive a notice that your email account will be purged. Soon after the notice, your account will be deleted. (There are a few exceptions; if you feel you need to keep your ODU email account, send an email to
its...@odu.edu.)
Google/Gmail: There is a 20 MB size limit imposed, meaning that no individual email can be larger than 20 MB. If you try to send a message with attachments that add up to more than 20 MB, the message will bounce. If someone tries to send you an email that is over 20 MB, it too will bounce.
Office365/Outlook: You can add email addresses and domains to your lists of blocked senders or safe senders. Go to
outlook.odu.edu and follow the instructions provided in this article from Microsoft: Filter junk email and spam in Outlook on the web
You may be seeing this page because you used the Back button while browsing a secure web site or application. Alternatively, you may have mistakenly bookmarked the web login form instead of the actual web site you wanted to bookmark or used a link created by somebody else who made the same mistake.
Outlook on the Web (OWA) is available for VUMC computers without access to the full Microsoft Office 365 experience, and to VUMC employees who need to login to their email when away from the main Medical Center network.
The Outlook on the Web (OWA) login page has two security options that allow you to indicate if you are using the software on a public or private computer. Your choice could be different depending on where you are. Please review the choices and their behaviors below:
3a8082e126