-
Posts
-
By Werct · Posted
Good, rooting for both sides -
By AsherGZ · Posted
They're too big to fail at this point. Even if Microsoft shutters entire divisions tomorrow, they'll be in the green for a long time because of how entrenched they are in the enterprise sector. Just look at politics. The people in charge are often some of the dumbest specimens humanity has ever produced. And yet, countries aren't crashing and burning every other day. -
By Usama Jawad96 · Posted
Exchange Online receiving one of its "most requested" features next month by Usama Jawad While most people are familiar with Outlook as their email client, especially within organizations deeply entrenched in the Microsoft stack, it is actually Exchange which powers the backend for this platform. What this means is that any enhancement to Exchange also gets flown downstream to Outlook. As such, Outlook users and IT admins will be pleased to know that Exchange Online is getting one of its "most requested" enhancements. Essentially, Message Recall will soon start working in cross-tenant environments. Previously, it only worked within a single tenant, which meant that if you wanted to recall an email accidentally sent to an external user, you were out of luck. Customers told Microsoft that they disliked this gap, especially when the two organizations emailing each other had trust between them. As such, Microsoft has decided to implement the Message Recall experience cross-tenant as well. Since the basis of this functionality is trust, IT admins will need to add each other in an allow list to enable this capability. Control rests with the recipient, so if Company A wants to recall a message sent to Company B, it is necessary that the latter adds Company A to the designated allow list. If they do not add the company to the allow list, recall attempts will fail with an appropriate error message. This feature is disabled by default, so IT admins will need to add at least one external tenant to their allow list first. The following Exchange Online PowerShell command will toggle cross-tenant Message Recall: Set-CrossTenantRecallConfiguration -CrossTenantRecallEnabled [$true | $false] And the cmdlet below will allow you to manage your allow list: Set-CrossTenantRecallConfiguration -AllowedSenderTenantIds @{Add="tenantId 1","tenantId 2"}; {Remove="tenantId 1","tenantId 2"} Cross-tenant recall works exactly as it does in intra-tenant environments. It is especially useful when communicating with trusted partners, subsidiaries, contractors, and more. Microsoft will begin rolling it out to worldwide, GCC, GCC High, DoD and Microsoft 365 environments operated by 21Vianet from mid-August, with completion planned for mid-September. -
By AsherGZ · Posted
Now that is just desperate LMAO. Throwing a tantrum just because you lost the AI race. Better focus on innovating than trying to stop competition from blazing past you. -
By jeff_pony · Posted
MS will replace open AI with their own models soon enough.
-
-
Recent Achievements
-
hadiaali45 earned a badge
Week One Done
-
arone_24 earned a badge
Week One Done
-
flexorcist earned a badge
Reacting Well
-
VitãoTub earned a badge
First Post
-
M S COMMUNICATION earned a badge
Week One Done
-
-
Popular Contributors
-
Tell a friend
.thumb.png.b7089ebbdf00d96b3b92dddbd04bac02.png)
Recommended Posts