Filip Kasaj

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Microsoft 365 Notes ======

Keeping Tabs on Azure AD Apps in Your Tenant\\
https://office365itpros.com/2023/06/14/app-governance-license

----


SharePoint Roadmap Pitstop: August 2022\\
https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/sharepoint-roadmap-pitstop-august-2022/ba-p/3617837

----

Microsoft Teams Rooms Pro and Microsoft Teams Rooms Basic, everything you need to know.\\
https://tomtalks.blog/microsoft-teams-rooms-pro-and-microsoft-teams-rooms-basic-everything-you-need-to-know/

----

MEC is back and my Petr is going to speak wow..\\
https://techcommunity.microsoft.com/t5/exchange-team-blog/wearemec-in-case-you-missed-it-mec-is-back-september-13-14/ba-p/3618751

----


Configure an automatic assignment policy for an access package in Azure AD entitlement management (Preview)\\
https://docs.microsoft.com/en-us/azure/active-directory/governance/entitlement-management-access-package-auto-assignment-policy

Tutorial: Manage access to resources in Azure AD entitlement management\\
https://docs.microsoft.com/en-us/azure/active-directory/governance/entitlement-management-access-package-first


----

How to Reset OneDrive Synchronization\\
https://petri.com/how-to-reset-onedrive-synchronization/

----


Microsoft Introduces Control Over Delegated Access to Encrypted Email\\
https://office365itpros.com/2022/06/09/delegate-access-encrypted-email/?utm_source=rss&utm_medium=rss&utm_campaign=delegate-access-encrypted-email\\

The control is in the form of a set of three new PowerShell cmdlets in the Exchange Online management module. These are:

  * Set-MailboxIRMAccess: Block a specified delegate from accessing encrypted messages in a user or shared mailbox.
  * Get-MailboxIRMAccess: Check if a block exists for a specified delegate in a user or shared mailbox.
  * Remove-MailboxIRMAccess: Remove a block from a user.

Delegate access to encrypted messages depends on the type of mailbox and how the delegate receives full access permission:

  * Outlook for Windows clients do not support delegate access to encrypted messages sent to user mailboxes. Delegates can only read encrypted messages if the sender includes the delegate as a TO or CC recipient. In this scenario, the delegate’s ability to read the message depends on the rights granted to them as a recipient. If the rights assigned to recipients include one applicable to the delegate, they can read the content. If not, they cannot.
  * Outlook for Windows clients support delegate access to encrypted messages sent to shared mailboxes if the delegate has full access and auto-mapping is specified when the delegate receives permission to the mailbox. Auto-mapping forces Outlook for Windows to open the shared mailbox as part of the resources available to the delegate. It is the default used by Exchange Online and is assigned when granting full access to a delegate for a mailbox using the Microsoft 365 admin center or Exchange admin center.
  * The other Outlook clients support delegated access to encrypted messages in both user and shared mailboxes if the delegate has full access to the mailbox.

----

TEMPORARY ACCESS PASS IS NOW AVAILABLE GENERAL AVAILABILITY\\
Service category: Multi-factor Authentication (MFA)\\
Product capability: User Authentication\\
Temporary Access Pass (TAP) is now generally available. TAPs can be used to securely register password-less methods such as Phone Sign-in, phishing resistant methods such as FIDO2, and even assist in Windows onboarding (Azure AD Join and Windows Hello for Business). TAPs also makes recovery easier when people have lost or forgotten their strong authentication methods and need to sign in to register new authentication methods.

PROTECT AGAINST BY-PASSING OF CLOUD AZURE AD MULTI-FACTOR AUTHENTICATION WHEN FEDERATED WITH AZURE AD GENERAL AVAILABILITY\\
Service category: Microsoft Graph\\
Product capability: Identity Security & Protection\\
Microsoft is delighted to announce a new security protection that prevents bypassing of cloud Azure AD multi-factor authentication (MFA) when federated with Azure AD.
When enabled for a federated domain in the Azure AD tenant, it ensures that a compromised federated account cannot bypass Azure AD multi-factor authentication (MFA) by imitating that multi-factor authentication has already been performed by the identity provider (IdP). The protection can be enabled via new security setting, federatedIdpMfaBehavior.

DYNAMIC GROUP SUPPORT FOR MEMBEROF PUBLIC PREVIEW\\
Service category: Group Management\\
Product capability: Directory\\
This feature enables admins to build dynamic Azure AD security groups and Microsoft 365 groups, based on memberships of other groups, For example, you can now create Dynamic-Group-A with members of Group-X and Group-Y.

ROLES ARE BEING ASSIGNED OUTSIDE OF PRIVILEGED IDENTITY MANAGEMENT PUBLIC PREVIEW\\
Service category: Privileged Identity Management (PIM)\\
Product capability: Privileged Identity Management (PIM)\\
Organizations can be alerted on assignments made outside Azure AD Privileged Identity Management (PIM) either directly on the Azure portal or also via email. For the current public preview, the assignments are being tracked at the subscription level.

NEW PROVISIONING CONNECTOR IN THE AZURE AD APPLICATION GALLERY\\
Service category: App Provisioning\\
Product capability: 3rd Party Integration\\
\\
https://dirteam.com/sander/2022/07/12/whats-new-in-azure-active-directory-for-june-2022/

----

Apps supported after January 10, 2023\\
Microsoft 365 Apps is supported under the Modern Lifecycle Policy. Therefore, the apps are supported continuously given that customers stay current per the servicing and system requirements. These requirements include using Microsoft 365 Apps on an operating system currently in support. On January 10, 2023, Windows 8.1 will reach the end of support. Also, on the same day, the three-year Extended Security Updates (ESU) paid program for Windows 7 and Windows Server 2008 R2 ends. While Microsoft 365 Apps is not currently supported on Windows 7 or Windows Server 2008 R2, we committed to provide security updates for the length of these ESU programs. Therefore, after January 10, 2023, Microsoft 365 Apps running on Windows 7, Windows 8.1, or Windows Server 2008 R2 will stop receiving security updates. Additionally, new installations of Microsoft 365 Apps will be blocked on Windows 8.1 devices… https://techcommunity.microsoft.com/t5/office-end-of-support-blog/act-now-and-keep-microsoft-365-apps-supported-after-january-10/ba-p/3568981

----

Windows Autopatch service GA\\
Windows Autopatch, an enterprise service that launched in public preview back in May, is now generally available for customers with Windows Enterprise E3 and E5 licenses. Microsoft’s new managed service enables IT Pros to automate the planning and deployment of Windows and Office updates. Essentially, Windows Autopatch uses deployment tools such as Windows Update for Business to manage updates for Windows 10, Windows 11, Microsoft Edge, Microsoft Teams, and other Microsoft 365 apps. It lets IT admins divide users into small groups called testing rings, monitor roll-out progress, and pause/roll back if needed…https://petri.com/microsofts-new-windows-autopatch-service-is-now-generally-available/

----

LOOP COMPONENTS OWA\\
Nine months after Loop components first appeared in Teams chat, the same components are available to include in OWA messages (message center notification MC360766, Microsoft 365 roadmap item 93234). The general availability date of June 2022 on the roadmap item is a tad optimistic as tenants configured for targeted release are only just seeing Loop components show up in OWA now. I have not seen Loop components show up in Outlook for Windows, bit according to Microsoft, general availability for Loop components in both OWA and Outlook for Windows is expected in July. That goal seems like quite a stretch.
The concept behind Loop components remains the same as in Teams chat. The author of a message inserts a component and edits its content. The physical instantiation of the component is a fluid file stored in the Attachments folder in the author’s OneDrive for Business account.
When they access a loop component, message recipients use a web sockets connection to receive changes made by others in almost real-time together with indicators to show where people are actively editing the content and where changes are made. A link in the message points to the file stored in OneDrive for Business and the app displays the content of the file in an inline editable frame… https://office365itpros.com/2022/07/12/loop-components-appear-owa/?utm_source=rss&utm_medium=rss&utm_campaign=loop-components-appear-owa

----

MC394512\\
To improve the consistency of experience and performance, any file with multiple versions that is deleted from SharePoint or OneDrive which is preserved to the Preservation Hold Library (due to its applicable retention label, retention policies or eDiscovery holds) will now be retained as a single file containing its full version history, rather than each version being retained as individual files as has been the case until now. https://petri.com/m365-changelog-microsoft-purview-data-lifecycle-records-management-ediscovery-rollout-update-optimized-file-version-behavior/