We are announcing enhancements to the unified pricing management data entity that will make pricing data imports and exports faster, more reliable, and easier to automate in Dynamics 365 Supply Chain Management. These enhancements will reach general availability on March 13, 2026. **How does this affect me?** This enhancement provides a refined data entity for importing and exporting Unified pricing management pricing rule data. It enhances data management framework mappings, data validations, and staging performance. The entity now supports clearer column semantics for price attributes and rule components, improved default mappings, and better error surfacing during high volume loads. These improvements streamline data imports and exports, reduce rework, and enable recurring jobs and data packages to move pricing configurations safely across environments. **Why is this action needed?** This message is for awareness, and no action is required. If you would like more information on this feature, please visit Optimize pricing data import and export workflows.

🚨 **Major Update:** This post contains a significant change that may impact your organisation. **[Introduction]** To maintain a high-quality and reliable experience for live **Captions & Subtitles** in the Microsoft 365 PowerPoint app, Microsoft is upgrading the backend service that supports this capability. As part of this improvement, older Office client versions will no longer be supported. Updating to the minimum required PowerPoint version ensures continued accessibility, performance, and reliability. **[When this will happen:]** Upgrade**** by the **end of September 2026** **[How this affects your organization:]** **Who is affected:** * Organizations using **Microsoft 365 PowerPoint app (Win32 or Mac)** * Users running PowerPoint versions earlier than: * Windows (Win32): **16.0.19426.20218** * macOS: **16.103.1207.4** **[What will happen:]** * Users on **unsupported versions** will**lose access to Captions & Subtitles** after the listed dates. * There is **no change** for users on **supported versions**. * **No changes to default settings** or admin configuration are required. **[What you can do to prepare:]** * Review PowerPoint client versions across your organization (Windows and Mac). * Update Office clients to: * Windows (Win32): **16.0.19426.20218 or later** * macOS: **16.103.1207.4 or later** * Plan upgrades ahead of **September 2026** , especially for environments on managed or restricted update cadences. * Notify helpdesk and accessibility stakeholders. **[Compliance considerations:]** No compliance considerations identified, review as appropriate for your organization.

We are announcing the ability to localize button and tab labels in POS screen layouts for multiple languages in Dynamics 365 Commerce. This feature will reach general availability on March 13, 2026. **How does this affect me?** This feature allows users to customize button and tab labels in any supported language directly within the Layout Designer, eliminating the need for duplicate layouts or manual code changes, ensuring that both Self-Checkout and assisted registers can deliver a tailored user interface for every audience. **What action do I need to take?** This message is for awareness, and no action is required.

We are announcing the ability to enable expense delegates to create cash advance requests in Dynamics 365 Project Operations. This feature will reach general availability on March 13, 2026. **How does this affect me?** This feature enables expense delegates to create and submit cash advance requests for other users. This feature can be turned on or off to meet the needs of your environment. **What action do I need to take?** This message is for awareness, and no action is required. If you would like more information on this feature, please visit Enable expense delegates to create cash advance requests.

🚨 **Major Update:** This post contains a significant change that may impact your organisation. **Introduction** To maintain security, performance, and long-term compatibility, Microsoft Teams on the web will require modern browser standards. Beginning **May 15, 2026** , Teams on the web will only be supported on browsers that are compliant with **ECMAScript 2022 (ES2022)**. **When this will happen** * **Now through May 14, 2026:** Users on unsupported browsers will see reminder banners. * **Beginning May 15, 2026:** Teams on the web will be blocked on non-compliant browsers. **How this affects your organization** **Who is affected:** * All tenants using **Teams on the web** * Users accessing Teams through **unsupported browser versions** * IT administrators responsible for browser standards and endpoint management **What will happen:** * Reminder banners will appear before enforcement. * Blocking page will appear starting**May 15, 2026** until the browser is updated. * The change is **enabled by default** and cannot be disabled. * Desktop and mobile Teams clients are **not impacted**. **What you can do to prepare** * Inventory browser versions used to access Microsoft 365 web apps. * Ensure users are on**supported browsers and versions**. * Notify helpdesk staff and end users ahead of enforcement. **Browser compatibility guidance** All currently supported versions of Microsoft Edge, Google Chrome, Mozilla Firefox, and Safari are **ECMAScript 2022 (ES2022)** compliant. Browsers that are out of vendor support should be assumed non‑compliant. A browser is considered “out of vendor support” when its publisher no longer provides updates or security fixes; these browsers should be assumed unsupported for Teams on the web. **Compliance considerations** Conditional Access policies may be impacted if users attempt access with unsupported browsers.

We are announcing the ability to automate production reporting with electronic sensors in Dynamics 365 Supply Chain Management. This feature will reach general availability on March 13, 2026. **How does this affect me?** This feature adds a new auto-reporting scenario for Sensor Data Intelligence. It allows manufacturers to augment production equipment by adding electronic sensors that automatically report production progress directly to Supply Chain Management. Admins configure the system by mapping each progress-tracking sensor to a specific machine resource and operation, choosing reporting intervals, and assigning unit-conversion factors. With this feature, workers using the production floor execution interface get real-time visibility into completed units. The solution supports two-level unit tracking for flexible use across various packaging setups, such as pieces per box and boxes per pallet. Users may switch to manual reporting at any time if needed. **What action do I need to take?** This message is for awareness, and no action is required. If you would like more information on this feature, please visit Automate production reporting with electronic sensors.

We are announcing the ability to calculate revenue recognition for stand-alone selling price contract lines in Dynamics 365 Project Operations. This feature will reach general availability on March 13, 2026. **How does this affect me?** This feature enables users to set the contract line value on the project's contract lines. The system calculates revenue recognition based on the contract line value amount. In revenue recognition, fixed-price billing arrangements are typically defined using billing milestones to establish the contract value. By separating the contract value from billing milestones, this feature allows users to recognize revenue based on the effort or stand-alone selling price. This approach aligns better with ASC 606 and IFRS 15 requirements. **What action do I need to take?** This message is for awareness, and no action is required. If you would like more information on this feature, please visit Calculate revenue recognition for stand-alone selling price contract lines.

We are announcing the ability to manage pricing rules using a generic base currency in Dynamics 365 Supply Chain Management. This feature will reach general availability on March 13, 2026. **How does this affect me?** This feature allows you to define a centralized price list in a generic base currency, avoiding the need to duplicate it for each transaction currency. The system automatically converts the generic currency price into the transaction currency using the latest exchange rates. **What action do I need to take?** This message is for awareness, and no action is required. If you would like more information on this feature, please visit Manage pricing rules using a generic base currency.

**[Introduction]** Starting in mid‑February 2026, the Microsoft 365 apps for Mac suite installer will include a shim for the Microsoft 365 Copilot app. This change helps organizations more easily deploy the Microsoft 365 Copilot Mac app by enabling users to download the full application** __** directly from the shim. The Microsoft 365 Copilot Mac app brings AI assistance to macOS, helping users search, analyze, and create from a single, secure desktop experience. **[When this will happen]** * **General Availability (Worldwide)** : Rollout will begin in **mid‑February 2026** and is expected to complete by **mid‑March 2026**. **[How this affects your organization]** _Who is affected_ : Organizations that deploy Microsoft 365 apps for Mac using the suite installation package. _What will happen_ : * The Microsoft 365 apps for Mac suite installer will include the Microsoft 365 Copilot shim app. * Users will be able to download and install the full Microsoft 365 Copilot app by opening the shim app from the **_Applications_** folder** _._** * Existing installations of Microsoft 365 apps on macOS are not affected. * Organizations that want to deploy Microsoft 365 Copilot to devices already running Microsoft 365 apps should deploy the shim app separately. **[What you can do to prepare]** If your organization deploys Microsoft 365 apps for Mac using the suite installer package: * Ensure the **Microsoft 365 Copilot shim app** is not excluded during deployment. * Confirm that **Microsoft AutoUpdate (MAU)** is enabled on macOS devices. * Confirm that devices meet the minimum requirement of **macOS 14.0 (Sonoma) or later**. * Ensure network connectivity is available so the shim app can download the full app. * This guidance is applicable for all users, not specifically those who want to deploy the shim app separately. * Review: Deployment guide for Office for Mac | Microsoft 365 | Microsoft Learn. **[Compliance considerations]** No compliance considerations identified. Review as appropriate for your organization.

🚨 **Major Update:** This post contains a significant change that may impact your organisation. Secure Boot is a foundational Windows security feature that runs at startup, before Windows load, and helps ensure that only trusted, digitally signed software can execute. After more than 15 years of continuous service, the original Secure Boot certificates are reaching the end of their planned lifecycle and begin expiring in late June 2026.To learn more about Microsoft’s effort to update these certificates, see the blog post Refreshing the root of trust: industry collaboration on Secure Boot certificate updates. To prevent disruption and maintain secure startup across Windows environments, plan for these certificates update following the guidance in the Secure Boot playbook.**When this will happen:** The 2011 Secure Boot certificates begin expiring in June 2026.**What you need to do to prepare:** Review the Secure Boot playbook for certificates expiring in 2026 to understand requirements, timelines, and supported scenarios. Additionally, bookmark https://aka.ms/GetSecureBoot for more information about this change, OEMs guidance, and answers to frequently asked questions.**Additional technical resources:** * If you use Microsoft Intune, read _Microsoft Intune method of Secure Boot for Windows devices with IT-managed updates._ * Compare this method to _Registry key updates for Secure Boot: Windows devices with IT-managed updates_. * Check out the option _Group Policy Objects (GPO) method of Secure Boot for Windows devices with IT-managed updates_. * See how these methods work together in _Secure Boot playbook for certificates expiring in 2026._

As part of our 10.0.46 and 10.0.47 releases, we have applied performance improvements to the adjustment process in Dynamics 365 Project Operations. These changes help project accountants start their next task with fewer delays after making adjustments. These performance improvements will be available to all customers by March 13, 2026. **How does this affect me?** Project accountants will experience faster transitions between tasks after adjustments, with fewer delays in starting subsequent work. **What action do I need to take?** This message is for awareness, and no action is required.

**[Introduction]** We are updating the filter pane in SharePoint Document Libraries and Lists to deliver a faster, more flexible filtering experience. The core functionality remains the same—users can continue filtering by metadata fields as before—but these improvements address performance issues and incorporate customer feedback for a more intuitive interface. Screenshot: _Side-by-side comparison of filter pane before and after changes_ **[When this will happen:]** * Targeted Release**:** Rollout begins **mid-February 2026** and is expected to complete by**late February 2026.** * General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins **late February 2026** and is expected to complete by **mid-March 2026**. **[How this affects your organization:]** **Who is affected:** All users of SharePoint Online Document Libraries and Lists. **[What will happen:]** The filter pane will automatically update in its existing location. Users will experience the following enhancements: * **Expand and collapse sections:** Control which filter sections appear. Users can expand or collapse individual sections or collapse all sections at once to quickly scan all available filters. * **See all filterable fields:** All filterable fields from library or list content will now display without limitations. Because fields are automatically shown, the ability to **pin** or remove filter fields has been removed. * **Enjoy better performance:** Filtering interactions are faster and more responsive across all libraries. Users continue to apply filters as before, including filtering by **person** , **date modified** , **content type** , and any custom metadata columns. **[What you can do to prepare:]** * Update internal documentation or training materials to reflect the new expand/collapse filter pane behavior and removal of the pin/remove filter field functionality. * Communicate these changes to helpdesk and support staff. * No admin action or configuration change is required. **[Compliance considerations:]** No compliance considerations identified; review as appropriate for your organization.

We are announcing the ability to use custom instructions for Microsoft Copilot ask a question in Dynamics 365 – Customer Service. This feature will reach general availability on February 28, 2026. **How does this affect me?** This feature allows you to define persistent preferences that guide how your Copilot agents respond across conversations. Instead of adapting on every prompt, you can specify upfront how you want your agent to behave with ask a question. This includes preferred tone, desired level of detail (e.g. summary vs. deep analysis), formatting preferences, role or context to assume, and constraints to follow. **What action do I need to take?** This message is for awareness, and no action is required.

🚨 **Major Update:** This post contains a significant change that may impact your organisation. **11:30 am PT update:**_Microsoft Store and Windows Update services have been restored. Some IT administrators may continue to experience residual latency affecting Windows Server update operations, including the Windows Server sync API. This Server‑specific issue is being addressed separately. If you experience this latency, please contact_ _Microsoft Support for business_ _._**8:34 am PT post:__** A power outage at a datacenter is impacting customers’ ability to complete operations in the Microsoft Store and Windows Update. As a result, some users may experience failures or timeouts when installing or updating Microsoft Store apps, or when downloading Windows updates.Although power has been restored, service recovery is still in progress. Storage services are gradually returning online, and some customer impact may continue while recovery completes.Microsoft is actively working to restore full-service reliability. Customers who are affected are advised to retry Microsoft Store and Windows Update operations later. We will provide more information as it becomes available.

🚨 **Major Update:** This post contains a significant change that may impact your organisation. **11:30 am PT update:**_Microsoft Store and Windows Update services have been restored. Some IT administrators may continue to experience residual latency affecting Windows Server update operations, including the Windows Server sync API. This Server‑specific issue is being addressed separately. If you experience this latency, please contact_ _Microsoft Support for business_ _._**8:34 am PT post:__** A power outage at a datacenter is impacting customers’ ability to complete operations in the Microsoft Store and Windows Update. As a result, some users may experience failures or timeouts when installing or updating Microsoft Store apps, or when downloading Windows updates.Although power has been restored, service recovery is still in progress. Storage services are gradually returning online, and some customer impact may continue while recovery completes.Microsoft is actively working to restore full-service reliability. Customers who are affected are advised to retry Microsoft Store and Windows Update operations later. We will provide more information as it becomes available.

<p><strong>[Introduction]</strong></p><p>To align with accessibility preferences and improve visual comfort for administrators, dark mode support is now coming to the SharePoint admin center. This update brings a consistent dark-themed experience similar to other Microsoft 365 admin portals.</p><p>This message is associated with Roadmap ID <a href="https://www.microsoft.com/microsoft-365/roadmap?filters=&amp;searchterms=552593#Roadmap">552593</a>.</p><p><strong>[When this will happen:]</strong></p><p>General Availability (Worldwide, GCC):<strong> </strong>Rollout begins <strong>mid-February 2026</strong> and is expected to complete by <strong>late February 2026</strong>.</p><p><strong>[How this affects your organization:]</strong></p><p><strong>Who is affected:</strong></p><p>SharePoint administrators who use the SharePoint admin center.</p><p><strong>What will happen:</strong></p><ul><li>A new dark mode option will become available in the SharePoint admin center.</li><li>Admins can switch between light and dark themes at any time.</li><li>This is an optional experience; the default theme remains unchanged.</li><li>No settings or controls are removed, and there is no impact to SharePoint end users.</li></ul><figure class="kg-card kg-image-card"><img src="https://cxcs.microsoft.net/file/ccp/en-us/24efd76f-7a52-43bb-9248-591930908085" class="kg-image" alt="user settings" loading="lazy" /></figure><figure class="kg-card kg-image-card"><img src="https://cxcs.microsoft.net/file/ccp/en-us/f8db2974-0a86-4cbf-af13-5fde3920a334" class="kg-image" alt="user settings" loading="lazy" /></figure><p><strong>[What you can do to prepare:]</strong></p><p>No preparation is required. </p><p><strong>How to enable dark mode in the SharePoint admin center:</strong></p><ul><li>Open the <strong>SharePoint admin center</strong> from the <strong>Microsoft 365 admin portal</strong>.</li><li>Select the <strong>Dark Mode </strong>switch located on the top right.</li></ul><p><strong>[Compliance considerations:]</strong></p><p>No compliance considerations identified, review as appropriate for your organization.</p>

<p>We are announcing the ability to strengthen bot protection for forms with reCAPTCHA in Dynamics 365 Customer Insights - Journeys. This feature will reach general availability on February 20, 2026.<br /><br /><strong>How does this affect me?</strong><br />This feature allows users to protect forms using reCAPTCHA, removing the need for outdated HIP CAPTCHA or custom technical work. Key capabilities introduced by this feature include:</p><ul><li>Add reCAPTCHA to any form using simple drag-and-drop drop in the Form Editor. No HTML edits or developer help is required.</li><li>Configure your Site key and Secret key once in default form settings to activate reCAPTCHA across all forms.</li><li>Protect form submissions with modern, widely trusted, accessibility-friendly bot detection.</li><li>Reduce spam, safeguard your customer data pipelines, and maintain higher form conversion rates.</li><li>Ensure compatibility with current security standards as HIP CAPTCHA is retired.</li></ul><p><strong>What action do I need to take?</strong><br />This message is for awareness, and no action is required.</p>

<p><strong>[Introduction]</strong></p><p>We are updating <strong>Microsoft Purview’s out-of-box (OOB) sensitive information type (SIT)</strong> detection logic to improve accuracy and reduce false positives. As part of this update, the relaxed proximity matching behavior previously used in some OOB SITs will be removed. After this change, all OOB SITs will consistently use stricter proximity rules for more consistent and precise detections.</p><p><strong>[When this will happen:]</strong></p><p><strong>General Availability (Production, GCC, GCC High, DoD):</strong> Available now</p><p><strong>[How this affects your organization:]</strong></p><p><strong>Who is affected:</strong></p><ul><li>Organizations using Microsoft Purview out-of-box sensitive information types in data classification or <strong>Data Loss Prevention (DLP)</strong> policies.</li></ul><p><strong>What will happen:</strong></p><ul><li>OOB SITs will stop using the relaxed proximity behavior previously applied in some detection rules.</li><li>All OOB SITs will consistently use stricter proximity matching rules going forward.</li><li>Content that previously matched under relaxed proximity conditions may no longer trigger a detection unless it meets the stricter proximity requirements.</li><li>This may result in fewer detections in scenarios that relied on broader proximity matching.</li><li>Custom sensitive information types are not affected and can still be configured to use broader proximity logic if required.</li></ul><p><strong>[What you can do to prepare:]</strong></p><ul><li>Review existing DLP and classification policies that rely on OOB SIT detections.</li><li>Test policy behavior in a non-production environment if broader proximity matching is required for certain workflows.</li><li>Create custom sensitive information types if your organization needs relaxed proximity logic.</li></ul><p>Learn more: <a href="https://learn.microsoft.com/purview/sensitive-information-type-learn-about">Sensitive Information Types in Microsoft Purview</a></p><ul></ul><p><strong>[Compliance considerations:]</strong></p> <table border="1" cellpadding="6" cellspacing="0"> <tbody><tr> <th><b>Question</b></th> <th><b>Explanation</b></th> </tr> <tr> <td>Does the change modify, interrupt, or disable Data Loss Prevention (DLP) policies or enforcement?</td> <td>Stricter proximity detection may reduce the number of matches, which could indirectly affect DLP behavior.</td> </tr> <tr> <td>Does the change modify Information Protection labels or sensitive information types?</td> <td>Out-of-box SITs are updated to retire relaxed proximity matching and use stricter proximity logic.</td> </tr> </tbody></table>

<div class="kg-card kg-callout-card kg-callout-card-red"><div class="kg-callout-emoji">🚨</div><div class="kg-callout-text"><strong>Major Update:</strong> This post contains a significant change that may impact your organisation.</div></div><p><strong>[Introduction]</strong></p><p>Microsoft Defender Antivirus on Windows is updating how antivirus configuration settings, such as exclusions, are stored when <strong>Microsoft Defender for Endpoint (MDE)</strong> configuration management is enabled. Starting with platform release <strong>4.18.25110.6</strong>, devices using MDE configuration management will no longer store readable exclusion values in the local device registry. Organizations must retrieve configuration using supported Microsoft Defender PowerShell cmdlets, such as <strong>Get-MpPreference</strong>.</p><p><strong>[When this will happen:]</strong></p><p></p><p>General Availability (Worldwide): We will begin rolling out <strong>early March 2026</strong> and expect to complete by <strong>late March 2026</strong>.</p><p><strong>[How this affects your organization:]</strong></p><p><strong>Who is affected:</strong></p><ul><li>Organizations using <strong>Microsoft Defender for Endpoint configuration management</strong>.</li><li>Admins or tools relying on <strong>registry-based monitoring</strong> of antivirus settings.</li></ul><p><strong>What will happen:</strong></p><ul><li>Antivirus exclusion values will <strong>no longer be readable</strong> from the local device registry.</li><li>Registry‑based extraction of exclusions will no longer be supported.</li><li>Supported Microsoft Defender PowerShell cmdlets (such as <strong>Get-MpPreference</strong>) will become the <strong>required </strong>method to retrieve antivirus configuration settings.</li><li>Devices not using MDE configuration management are <strong>not affected</strong>.</li><li>The feature is <strong>on by default</strong> for tenants using MDE configuration management.</li></ul><p><strong>[What you can do to prepare:]</strong></p><ul><li>Update monitoring workflows and scripts to use supported PowerShell cmdlets such as:<ul><li> <code>Get-MpPreference</code></li><li><code>Get-MpComputerStatus</code></li></ul></li><li>Review internal documentation on retrieving antivirus settings.</li><li>Notify helpdesk or monitoring teams that registry-based queries will no longer return exclusion data.</li></ul><p>Learn more: <a href="https://learn.microsoft.com/defender-endpoint/troubleshoot-settings#step-3-identify-policies-or-settings">Troubleshoot Microsoft Defender Antivirus settings - Microsoft Defender for Endpoint | Microsoft Learn</a> (will be updated to reflect this change)</p><p><strong>[Compliance considerations:]</strong></p><p>No compliance considerations identified, review as appropriate for your organization.</p>

<p>I've been playing around with Azure File Shares recently. Mostly for work purposes, but also for play... In my own tenant, I predominantly use SharePoint and OneDrive for all our storage needs, but as I've been toying around with Azure Files in my work tenant, I thought to myself "how easily would this slot into my personal tenant?".</p><p>The answer? Very easily.</p><p>But how does Cloud Kerberos come into this, and macOS? Well... macOS, obviously, isn't a Windows system. So, when it comes to authenticating against Entra ID, there's several hoops we jump through to get this working.</p><p>One of those, is Platform SSO. (A requirement for Cloud Kerberos btw).</p><p>Platform SSO is the piece of the puzzle that allows single sign on to all our Microsoft resources, from all Microsoft and built-in system apps in macOS. You sign in once, you sign in everywhere!</p><p>Once Platform SSO is configured, you can easily configure Cloud Kerberos.</p><p>Cloud Kerberos, in my example at least, allowed me to seamlessly authenticate against an Azure Files Share in macOS without having to authenticate with secret keys, or static usernames and passwords. It authenticates with my logged in user, the same user I used to authenticate against Platform SSO.</p><p>No prompts, no authentication messages, just straight access to my File Share.</p><p>So, without further ado, let me show you how to get it configured... with Microsoft Intune!</p><h2 id="configuring-the-policy-in-microsoft-intune">Configuring the Policy in Microsoft Intune</h2><ol><li>You're going to start by heading to the Microsoft Intune Admin Center. And heading to the Devices &gt; macOS &gt; Configuration section.</li></ol><figure class="kg-card kg-image-card"><img src="https://blog.tophhie.cloud/content/images/2026/02/image.png" class="kg-image" alt="" loading="lazy" width="1765" height="1043" srcset="https://blog.tophhie.cloud/content/images/size/w600/2026/02/image.png 600w, https://blog.tophhie.cloud/content/images/size/w1000/2026/02/image.png 1000w, https://blog.tophhie.cloud/content/images/size/w1600/2026/02/image.png 1600w, https://blog.tophhie.cloud/content/images/2026/02/image.png 1765w" /></figure><ol><li>Create a new "Settings Catalog" policy.<ol><li>Give it a meaningful name like "Entra ID Cloud Kerberos Tickets", or whatever floats your boat!</li></ol></li><li>Add the following settings from Authentication &gt; Extensible Single Sign On Kerberos.<ol><li>Extension Identifier</li><li>Hosts</li><li>Realm</li><li>Team Identifier</li><li>Type</li><li>Extension Data<ol><li>Allow Automatic Login</li><li>Allow Platform SSO OAuth Fallback</li><li>Perform Kerberos Only</li><li>Preferred KDCs</li><li>Sync Local Password</li><li>Use Platform SSOTGT</li></ol></li></ol></li><li>Configure the settings as follows:<ol><li>Allow Automatic Login - <strong>True</strong></li><li>Allow Platform SSO Oauth Fallback - <strong>Enabled</strong></li><li>Perform Kerberos Only - <strong>True</strong></li><li>Preferred KDCs<ol><li>kkdcp://login.microsoftonline.com/YOUR TENANT ID/kerberos</li></ol></li><li>Sync Local Password - <strong>False</strong></li><li>Use Platform SSOTGT - <strong>Enabled</strong></li><li>Extension Identifier - <strong>com.apple.AppSSOKerberos.KerberosExtension</strong></li><li>Hosts<ol><li>Your primary domain</li><li>*.Your primary domain</li><li>windows.net</li><li>*.windows.net</li><li>kerberos.microsoftonline.com</li><li>microsoftonline.com</li><li>*.microsoftonline.com</li></ol></li><li>Realm - <strong>KERBEROS.MICROSOFTONLINE.COM</strong></li><li>Team Identifier - apple</li><li>Type - Credential</li></ol></li></ol><p>Your policy should look a little something like this!</p><figure class="kg-card kg-image-card"><img src="https://blog.tophhie.cloud/content/images/2026/02/image-1.png" class="kg-image" alt="" loading="lazy" width="743" height="1113" srcset="https://blog.tophhie.cloud/content/images/size/w600/2026/02/image-1.png 600w, https://blog.tophhie.cloud/content/images/2026/02/image-1.png 743w" /></figure><ol><li>Assign this policy to your users (not devices).</li></ol><p>Once this has been applied to your users, and the policy has hit their devices, I've found a reboot is often necessary to get the Kerberos tickets queried and refreshed. But once that's done, you should find you can now access resources that require Kerberos tickets!</p><p>You'll know the policy has applied because a "key" will appear in the Menu Bar, and when you click on it, it'll tell you you're signed in!</p><figure class="kg-card kg-image-card"><img src="https://blog.tophhie.cloud/content/images/2026/02/image-2.png" class="kg-image" alt="" loading="lazy" width="927" height="672" srcset="https://blog.tophhie.cloud/content/images/size/w600/2026/02/image-2.png 600w, https://blog.tophhie.cloud/content/images/2026/02/image-2.png 927w" /></figure><p>And that's it! You've configured Entra ID Cloud Kerberos for macOS!</p><p>Until next time 👋🏻</p>

<p>We are announcing the ability to trigger forecast scenarios on demand in Dynamics 365 Customer Service. This feature will reach general availability on February 27, 2026.<br /><br /><strong>How does this affect me?</strong><br />Supervisors will be able to generate up-to-date forecasts during planning and operational reviews without waiting for scheduled runs. This feature allows supervisors to initiate the "Run forecast scenario" action, which starts a background job to generate the forecast asynchronously. After the job completes, updated forecast outputs will be available in forecast reports and views. The completion of the forecast run also triggers a capacity planning job to refresh staffing requirements based on the latest forecast output.<br /><br /><strong>What action do I need to take?</strong><br />To use this feature, you must install the <em>Workforce Management for Customer Service</em> package from the Power Platform admin center.<br /><br />If you would like more information on this feature, please visit <a href="https://aka.ms/13853/1">Create and manage forecast scenarios</a>.</p>

<p><strong>[Introduction]</strong></p><p>Microsoft is introducing a unified <strong>plus (+) menu </strong>to make it easier for users to add grounding, tools, and sources when prompting in Microsoft 365 Copilot. Grounding refers to the content users connect to Copilot—such as files, sites, or other organizational data—that helps improve response relevance. This update consolidates related actions into a single menu, improving discoverability and streamlining the workflow for adding entities or updating inputs. This simplified menu will be available for Copilot Chat users (without a Microsoft 365 Copilot license) and Microsoft 365 Copilot users (with a Microsoft 365 Copilot license).</p><figure class="kg-card kg-image-card"><img src="https://cxcs.microsoft.net/file/ccp/en-us/35da0d3a-4996-46b4-9042-ca643735bdee" class="kg-image" alt="user settings" loading="lazy" /></figure><p>Note: The <strong>Tools menu</strong> will be consolidated under the unified <strong>plus (+) menu</strong> and no longer exist as a separate menu in the prompt box after this change.</p><p><strong>[When this will happen:]</strong></p><p>General Availability (Worldwide): Rollout begins in<strong> late February 2026</strong> and is expected to complete by <strong>mid‑March 2026</strong>.</p><p><strong>[How this affects your organization:]</strong></p><p>  <strong>Who is affected:</strong></p><p>  Copilot Chat and Microsoft 365 Copilot users that rely on the unified <strong>plus (+) menu</strong>.</p><p>  <strong>What will happen:</strong></p><ul><li>Users will see a redesigned and unified <strong>plus (+) menu</strong>.</li><li>Grounding options, tools, and data sources will be consolidated in one menu.</li><li>Users will be able to add entities and update sources from this unified location.</li><li>The feature will be <strong>enabled by default </strong>and replaces the current experience; no admin configuration is required.</li><li>Existing admin policies related to Copilot input sources remain unchanged.</li></ul><p><strong>[What you can do to prepare:]</strong></p><p>No action is required for administrators.</p><ul><li>Inform helpdesk and training teams about the unified <strong>plus (+) menu</strong> layout.</li><li>Update internal documentation or screenshots that reference the previous menu.</li></ul><p><strong>[Compliance considerations:]</strong></p><p>No compliance considerations identified, review as appropriate for your organization.</p>

<div class="kg-card kg-callout-card kg-callout-card-red"><div class="kg-callout-emoji">🚨</div><div class="kg-callout-text"><strong>Major Update:</strong> This post contains a significant change that may impact your organisation.</div></div><p></p><p></p><p></p><p><strong>[Introduction]</strong></p><p></p><p><strong>Project Online will be retired on September 30, 2026. </strong>As part of this retirement process, <strong>starting April 1, 2026</strong>, we’re making changes to Project Web App (PWA) site creation and access. These changes support a smooth and predictable retirement experience, reduce unused resource consumption, and help organizations transition to modern project management solutions in <em>Microsoft 365</em>.</p><p><strong>[When this will happen]</strong></p><p>These changes will take effect <strong>starting April 1, 2026,</strong> and will remain in effect as part of the Project Online retirement process.</p><p><strong>[How this affects your organization]</strong></p><p><em>Who is affected: </em></p><p></p><ul><li>Microsoft 365 tenants using <strong>Project Online</strong> and <strong>Project Web App (PWA)</strong>.</li></ul><p><em>What is changing on April 1, 2026:</em></p><ul><li><strong>Creation of new PWA sites will be blocked</strong>. Users will no longer be able to create new Project Online PWA site collections.</li><li><strong>Unused PWA sites will be blocked and become inaccessible</strong>. Any existing PWA site that does not contain at least one project will be blocked.<ul><li>Non-PWA content stored in these sites will still be accessible.</li></ul></li><li><strong>Active PWA sites will not be affected</strong>. Sites that contain one or more projects will continue to function until Project Online is retired.</li><li><strong>No admin action is required to enable these changes</strong>. Enforcement begins automatically on <strong>April 1, 2026</strong>.</li></ul><p><strong>[What you can do to prepare]</strong></p><p></p><p>To ensure continued access to the PWA sites your organization relies on:</p><ul><li>Review your existing Project Online PWA sites.</li><li>Identify PWA sites that do not contain any projects.</li><li>If you want a PWA site to remain accessible, create at least one project in that site <strong>before April 1, 2026</strong>.</li><li>Inform Project Online administrators, PMO teams, and support staff about this change.</li><li>Update internal documentation related to Project Online usage and provisioning workflows.</li></ul><p>If no action is required for your organization, you may continue using Project Online until its retirement on <strong>September 30, 2026</strong>.</p><p></p><p></p><p>Learn more about the retirement here - <a href="https://techcommunity.microsoft.com/blog/plannerblog/microsoft-project-online-is-retiring-what-you-need-to-know/4450558">Microsoft Project Online is retiring: What you need to know | Microsoft Community Hub</a></p><p><strong>[Compliance considerations]</strong></p><p>No compliance considerations identified. Review as appropriate for your organization.</p>

<p><strong>Introduction</strong></p><p>We’re conducting an experiment that changes how Word, Excel, and PowerPoint file attachments open in Outlook for iOS and Android. For <strong>iPad users only, </strong>these files may open directly in the Word, Excel, or PowerPoint apps when they are installed, instead of using the in-app previewer.</p><p><strong>When this will happen:</strong></p><p>General Availability (Worldwide, GCC, GCCH, DoD): We will begin rolling out this experiment in <strong>early to mid-February 2026</strong> and expect to decide whether to proceed with or stop the rollout by the <strong>late March 2026</strong>.</p><p><strong>How this affects your organization:</strong></p><p><strong>Who is affected:</strong></p><ul><li>Users on <strong>iPad devices</strong> running Outlook who have the Word, Excel, or PowerPoint apps installed.</li></ul><p><strong>What will happen:</strong></p><ul><li>Some iPad users will find that Word, Excel, and PowerPoint attachments open directly in the corresponding app.</li><li>Users without the Office apps installed will continue to use the in-app previewer.</li><li>This is an experiment and may not become permanent.</li><li>No admin configuration is required.</li></ul><p><strong>What you can do to prepare:</strong></p><ul><li>No action is required.</li><li>You may choose to notify iPad users or update internal help documentation.</li></ul><p><strong>Compliance considerations:</strong></p><p>No compliance considerations identified, review as appropriate for your organization.</p>

<p>We've released updates to the following update channel for Microsoft 365 Apps:</p><ul><li>Current Channel</li></ul><h2 id="when-this-will-happen">When this will happen</h2><p>We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting February 3rd, 2026 (PST).</p><h2 id="how-this-will-affect-your-organization">How this will affect your organization</h2><p>If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.</p><p>If you manage updates directly you can now download this latest update and begin deployment.</p><h2 id="what-you-need-to-do-to-prepare">What you need to do to prepare</h2><p>To get more details about this update view the following release notes:</p><ul><li><a href="https://docs.microsoft.com/officeupdates/current-channel#version-2601-february-03" rel="noopener noreferrer">Current Channel</a></li></ul>