Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
microsoft entra
25 TopicsChrome passkey popup
I have this issue where Chrome's passkey popup overlays 1Password. The device is Entra joined and the passkey is bound to the device. Deleting the passkey in Windows settings is not an option. Everytime i visit a Microsoft login page the Chrome passkey popup also shows over 1Password. This only happens when using Windows 11 + Chrome. Using Windows 11 + Microsoft Edge does not show any popup from MS. 1Password is set as the default password manager in Chrome Any recommendations? 1Password Version: 8.12.10 Extension Version: 8.12.12.44 OS Version: Windows 11 25H2 | 26200.8246 Browser: Chrome 124.0.7444.163Solved56Views0likes3CommentsEdge Authentication Window when using Microsoft SSO
Hello! We have configured Microsoft/EntraID SSO for login to 1Password. The users are logged in to the Windows PC with an Active Directory User - the Users are synchronized to EntraID, where SSO with 1Password is configured. Recently we are experiencing the issue, that for every first 1Password unlock after a PC restart, when we click "Login with Microsoft" in 1Password, a Browser window opens, asking for the Microsoft 365/EntraID login credentials. The login to 1Password is successful anyway, either if we enter the credentials in this window, or if we do not enter any credentials and close the window. How can we prevent that Browser window asking for credentials? Is there something we need to configure on 1Password side? Thank you and best regards, Michael11Views0likes0CommentsManaged Update of Intune Win32 App
I deploy 1Password via Intune, and I recently transitioned our deployment from the MSI installer to the MSIX installer—as a Win32 app in both cases. I prefer to manage the deployed version and so disable Auto Update. When deploying using the MSI installer, I used a File detection rule that checked for the presence of the app and also checked the version. Rule type: File Path: C:\Program Files\1Password\app\8 File or folder: 1Password.exe Detection method: String (version) Operator: Greater than or equal to Value: 8.x.x Associated with a 32-bit app on 64-bit clients: No With this process, when I updated the installer version, I would update the version value in the detection rule, and Intune would update the installed version of 1Password when it detected a version number less than the expected value. Because the detection script provided for the MSIX deployment—AppDetectScript.ps1—does not include a version check, updating the installer version has no effect on devices where 1Password is already installed. Intune will report that the latest version is installed, but that is only because it is finding 1Password, not because it is finding the latest version of 1Password. I modified the script to include a version check, in hopes that that Intune would then behave as it had with the MSI installer, installing the latest version of the app when it detected that the installed version did not match the target version. # Modify the $targetVersion to ensure app updates $targetVersion = "8.12.10" $targetVersion = [Version] $targetVersion.ToString() # The unique 1Password identifier in detection scripts. $targetPackageFamilyName = "Agilebits.1Password_amwd9z03whsfe" try { # Per-user install (eg. Install behavior in Intune is User). $package = Get-AppxPackage | Where-Object { $_.PackageFamilyName -eq $targetPackageFamilyName } if ($package) { $ver = [Version] $package.Version.ToString() Write-Host "1Password is installed." if ($ver -ge $targetVersion) { Write-Host "1Password is up to date." exit 0 } else { Write-Host "1Password requires an update." exit 1 } } else { Write-Host "A 1Password installation wasn't found." exit 1 } } catch { Write-Host "An error occurred when detecting a 1Password installation: $_" exit 1 } As far as I can tell, the detection script worked, in the sense that it started registering the app as not installed—"The application was not detected after installation completed successfully"—but it did not cause the installed version to be updated. I know that the https://support.1password.com/deploy-1password/?windows#step-1-plan-your-deployment-windows states: To allow your team members to update 1Password, deploy the MSIX as a Win32 app and set the install behavior to User. To manage and deploy updates to 1Password, deploy the MSIX as a line-of-business app and set the install behavior to User. But all of our other Intune app deployments are Win32 apps, and, https://learn.microsoft.com/en-us/intune/intune-service/apps/apps-win32-troubleshoot#:~:text=If%20you%20mix%20the%20installation%20of%20Win32%20apps%20and%20line%2Dof%2Dbusiness%20(LOB)%20apps%20during%20Windows%20Autopilot%20enrollment%2C%20the%20app%20installation%20might%20fail., Win32 and LOB apps do not mix well when using Windows Autopilot (which we do): If you mix the installation of Win32 apps and line-of-business (LOB) apps during Windows Autopilot enrollment, the app installation might fail. I was hoping it might just work. Since it seems as though that is not the case, I was wondering if there is a technical reason why the MSIX deployment does not work as the MSI deployment did, if there is a chance that modifying the detection script in some way could work, and, given the answers to the first two questions, if there is some way this setup might be made to work in the future?33Views0likes0CommentsSystem Down due to Expired Client Secret
I'm in desperate need of some support here. Our Notion alert that the client secret for our 1Password Entra ID SSO was expiring did not alert like it should have and we are now all locked out. There seems to be no way to bypass and use the emergency kit to update the integration in 1Password. I have opened a support ticket, but it isn't moving fast enough. Is there a way for Administrators to bypass SSO and get back in using the emergency kits that I'm missing?28Views0likes0CommentsCannot Complete User Recovery
Hello, We have a user that was put into recovery and completed their steps via email. However, when an admin tries to complete the recovery, this error pops up. This has been consistent over the past 48 hours for this specific user. We use Azure SSO with a SCIM. Any help would be greatly appreciated.Solved53Views0likes2CommentsManaged Browser Extension
Hey all, New to 1Password for Business, long time 1Password personal user. I've just kicked off migration of legacy password manager (on-prem) for about 500 users in a Microsoft Intune full cloud environment. Our org has strict management over our Windows 11 devices... (you know, any HR opportunity to educate staff starts with I.T doing all the work with tech removing any need to teach users how to do something) I need to manage the browser extension, the usual default save vault location and watchtower etc. i thought i was on a winner with MDM ADMX - https://support.1password.com/mobile-device-management/?windows#appendix-set-the-default-vault-for-saving-new-items but this looks to be the full app rather that anything for the extension? How can i directly manage the extension via Intune?50Views0likes0CommentsMicrosoft Entra ID SSO issue
We have recently migrated all our users over to using Microsoft Entra ID SSO. It works fine except every time they close the app or shutdown their computer, it asks them to login using SSO. We have a set of employees who do not always have a connection available. They go from site to site and some basements where they need to go don't have network or wi-fi. When that happens, they are unable to use 1password. Keep in mind that most of the time when they access these places they are escorted by security to go down in the basements and it's wasting their time as well as the security employee. We have it set to ask the Entra password every 7 days. Expected behavior: if I close the app or restart the computer, the token should still be valid. Current behavior: Every time I close the app or restart the computer, I have to login to the microsoft account again.95Views1like1Comment"Installation stopped. 1Password is already installed on this device" Notification
Good morning, Multiple users, including myself, are receiving this error: After clicking, "Yes" the pop-up will come back sometime later. We are deploying 1Password via Intune (Windows Store App). How can I get this pop-up to go away?Solved389Views0likes10CommentsInterferes with Microsoft Company Portal Passkeys
1Password extension interferes with the passkey flow for Microsoft Entra / Company Portal. This flow integrates with the system passkey dialogue, which 1Password attempts to subvert. Depending on the exact scenario one of three things seems happen: When fully logged out and logging into a generic Microsoft login form (such as logging into accounts.microsoft.com, 1Password always attempts to replace the Company Portal passkey flow When logged in but re-verifying, and 1Password is locked then it still attempts to replace the Company Portal passkey flow When logged in but re-verifying, and 1Password is unlocked then it sees that there's no matching passkey and doesn't interfere Please either fix these issues or switch to the system passkey prompt on Mac which doesn't have this issue.20Views0likes0Comments