Outlook for iOS + Caller Identification
Hey folks, i'm struggling at this for years, as you can see in my previus post from 2020. Let me shorten this: Scenario We have iOS Devices with Outlook for iOS installed. The users have many contacts in their EXO Mailboxes When a user gets a call from one of his contacts, the phone number is presented instead of the name (no Caller identification) Approaches I already know this MS articles belonging to Contact Sync. So i've learned that this leads to a running contact sync without the need of an icloud Account. The contacts could be written directly between Outlook for iOS and the native contacts app. (Better than nothing ) The Problem is, that if contact sync is in use ANY App could see these contacts. (Including Whatsapp, etc...) Because of GDPR this is a no-brainer. Many other solutions are using Apple Call-Kit, so that the incoming call is identified (name is shown) just without any need of contacts to be present in the native contact app. I didn't found anything belonging Call-Kit or any other possible solution for this issue, yet. There MUST be any better solutions except syncronizing all the contacts, isn't it? ANY Answer is highly appreciated. (At least the positive ones ) Regards, Patrick!
Stop Users Adding Exchange Email Addresses
Hi All, Is there a way to stop users in Outlook 365 from adding Exchange email addresses that are not their sign in address?? or is there a way to just block the accounts wizard? I know we can block a range of other email address types, but I don't want people adding any other mailboxes to their work PC's. Hopefully someone has an answer. Thanks!
Outlook Mobile App updating network password on Android Work side
When a user updates their network password in Active Directory, where do you go into the phone and update the password or even just rekey to make sure its accurate? I know on the iPhone you do it from within the Outlook Mobile App. Where do you go for the Androids? I went into Accounts and went to work side but dont see where you can update it in there.
New Teams and Outlook not working for my organization.
Hi All. I've been trying to allow the New teams/Outlook for my organization. Here's how we curently have everything setup: We use Windows Information Protection with enrolled devices. WIP works with “classic” version of MS Teams and Outlook but not the latest “new” version that is being rolled out. We know that it relates to WIP, as both new versions work fine with WIP turned off. We don’t seem to able to add the correct details to the WIP policy in order to add the new MS Team and Outlook as protected apps (enlightened or unenlightened); they keep showing as “personal” in Task Manager “Enterprise Context”. These are the configurations that I've tried so far and didn't seem to work for both apps. Outlook Name: Outlook Product name: microsoft.windowscommunicationsapps Type: Universal app Publisher: CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US Min Version: * Max Version: * Action: Allow Teams Name: Microsoft Teams Product name: * Type: Desktop apps Publisher: O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US File: ms-teams.exe Min Version: * Max Version: * Action: Allow Is there anyone who can advise with the WIP config or is there an alternative way to get the users to switch to the new Apps? Thank you.
Intune Kontakte im Arbeitsbereich werden nicht aufgelöst
Hallo, Wir haben das folgende Problem: Wir verwenden Intune für Android, und im Arbeitsbereich habe ich das folgende Phänomen: Wenn die Kontakte von Outlook auf das Handy synchronisiert werden, kann ich alle Kontakte nach Namen durchsuchen, aber wenn mich jemand anruft, sehe ich nur die Telefonnummer. Es gibt keine Namensauflösung. Können Sie mir helfen, wie ich dieses Problem lösen kann? Danke, BenceBlock any email clients on Windows except Outlook Web
Greetings, I'm opening this discussion to speak about how to block access to Exchange Online from any email client (Outlook, Windows 10 Mail, new Outlook for Windows, third-party client) on Windows devices (either Intune-unmanaged, Intune-managed, Microsoft Entra joined, Microsoft Entra registered, Microsoft Entra hybrid joined). Outlook web is only allowed. TEST 1 My initial attempt, as mentioned in this post how to block the Outlook desktop app while allow them use the Outlook On the Web (OWA), was to block access through a Conditional Access policy. Target resources: Office 365 Exchange Online Conditions > Device platforms: Windows Phone, Windows, Linux Conditions > Client apps: Mobile apps and desktop clients, Exchange ActiveSync clients, Other clients Grant: Block access Results: I realized it isn't applicable because even if it meets the goal, however it is also blocking applications like Microsoft Teams. TEST 2 I modified the CA policy by allowing access from compliant devices or hybrid joined: Target resources: Office 365, Office 365 Exchange Online and Office 365 SharePoint Online Conditions > Device platforms: Windows Phone, Windows, Linux Conditions > Client apps: Mobile apps and desktop clients, Exchange ActiveSync clients, Other clients Grant: Grant access to Require device to be marked as compliant, Require Microsoft Entra hybrid joined device (Require one of the selected controls) Results: In this way, I can force clients to be compliant (Intune-managed) or hybrid joined, at least; however, I cannot control access from email clients (consider, for example, a scenario in which end-users have Outlook installed for opening file in MSG or EML format). TEST 3 The only way I found to achieve the goal was to take action on Exchange Online, by manipulating these properties for each mailbox via PowerShell (Set-CASMailbox) : MAPIEnabled = false (block Outlook) UniversalOutlookEnabled = false (block Windows Mail app) OneWinNativeOutlookEnabled = false (block new Windows Mail app) It seems even if blocked (2), however I can still configure and access to mailbox via Windows Mail. I also realized (Welcome Sir !!! 🙂) even if the above properties appear at Plan level (Get-CASMailboxPlan), however it isn't possible to set them (Set-CASMailboxPlan); but it is possible to disable, for example, IMAP and POP (?), This solution assumes running a PowerShell script for setting these properties on new mailbox creation. Any other suggestion ?
App protection (WIP) - Outlook - Can't use work content here
Hello, We've successfully implemented M365 Apps and applied App protection policies (WIP with enrollment). All components are functioning as anticipated, with the exception of M365 Outlook. Our users are encountering an issue when they attempt to attach files from OneDrive or paste text from a work document. They receive a warning message that reads, "Can't use work content here. Your organization doesn't allow you to use work content here." Interestingly, this problem arose following our migration from Outlook 2016 to M365 Outlook. A peculiar observation is that pasting text from the work context into the "To", "Cc", or "Subject" fields works without any issue, but doing the same into the body of the e-mail is not permitted. Any assistance or guidance on this matter would be appreciated. Thank you.
