User Profile
teward001
Copper Contributor
Joined 3 years ago
User Widgets
Recent Discussions
RDWeb HTML5 client on On-Prem Deployment: Change internal resource URLs to public ones.
On our RDWeb HTML5 deployment per https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client-admin#how-to-pre-configure-settings-for-remote-desktop-web-client-users we have set up the client. However, while our RDGateway and other components are all set to 'connect.example.com' for the URL and server name to use, the RDWeb client is defaulting to rdgateway01.internalonly.example.com which isn't usable from the outside. As such, connections that aren't on our internal VPN or internal network are failing. With the old (and I mean REALLY old) preview versions, this URL the system is using for the logon page, etc. was the correct 'connect.example.com' settings. Since the new version, however, it looks like there's no way to configure this. Is there any way to tell RDWeb to use the proper URL publicly rather than use the internal FQDN that is NOT set in the RD Gateway and RD Broker systems?330Views0likes0CommentsRe: Exchange Online Plan 2 and Standalone Outlook?
I'll raise that with my client - I'm on an E5 but my client has been working with on-prem mail and has only just started considering MS365 for their mail - E1 makes sense for then as well and I'll include that in the options I share in my analysis to them. The life of being a consultant and full time security guy makes it such that it is likely what I have is different than the clients have. 🙂4.6KViews0likes0CommentsRe: Exchange Online Plan 2 and Standalone Outlook?
Nice, thanks for the confirm. Things like IRM require the Exch Online Protection licensing anyways and the client was after email with antimalware and antispam so that's Exchange Online Plan for their needs. Thanks for confirming what I had thought.4.5KViews0likes0CommentsExchange Online Plan 2 and Standalone Outlook?
I have a client who has a license for Office Pro 2019 and uses it for office stuff. They are looking to get MS365 email set up instead of an onprem IMAP setup. They were looking at Exchange Online Plan 2 licenses for their needs as they already have Office licensing. Will their standalone Oulook integrate wirh the Exchange Online Plan 2 licenses in the sense that outlook desktop client will function with their exchange online they intend to buy?Solved5.5KViews0likes4CommentsEmail Encryption: Disable MS365 logins and force OTP codes via email
Currently, all outgoing encrypted emails are required to use MS365 login for *any* MS365-enabled tenants. This is a problem, because we can't use this with external tenants for some reason - it's not clear why, but there's a lot of external tenants who are failing to authenticate. We know that this is sometimes due to internal team/distro lists at external tenants not being able to login/auth. However, *historically*, we were able to select "Login with Microsoft Account" or "Receive OTP code via email". In the modern Purview environment, it doesn't seem that changing settings in OME settings or IRM settings will allow you to actually disable social logins and force OTP codes as the only mechanism. Whether this is due to the way Purview policies are set up for "Encrypt" profile or not, I don't see a way to change this and force *only* OTP. Is there any way to disable all social ID login **including MS365 logins** for encrypted messages, and force only OTP codes?1.1KViews0likes0CommentsUsing Email Encryption: Remote tenants not able to authenticate / open encrypted messages
We are using automation plus a flow rule to force encrypted emails via flow rules that apply Office 365 Message Encryption and Rights Protection with the "Encrypt Only" policy. However, when we send to people who are on remote tenants, we run into an unusual problem. Some tenants "just work", while other tenants hard fail with a notice that says the following: Selected user account does not exist in tenant 'Tenant Name' and cannot access the application 'UUID Here' in that tenant. The account needs to be added as an external user in the tenant first. Please use a different account. Unfortunately, there's no option to bypass this for those recipients and no way to force one time password authentication options where they have to request a OTP and then use that. It enforces the use of MS365 Tenant auth rather than OTP, which is unusual and problematic because while *certain* remote tenants "just work" others do not. I'm confused as to where to look next. Is there a way to force OTP-only in the outgoing encryption for a message with transport rules on the Outlook 365 admin panel? Alternatively, is there a way to automatically permit external tenant accounts/recipients to just work? Please feel free to ask any questions necessary to solve this on our end, it's a core component of one of our information sending systems to partners and it's not working as intended.1.2KViews0likes1Comment
Recent Blog Articles
No content to show