When the audio pipeline decides to act up đđ¤
Ever since build 2820.x.x.x, Iâve been keeping an eye on one specific process â Audio Graph Isolation. And this little troublemaker đ sometimes decides it wants to âspice up your day.â Not by taking a few MB of RAM⌠Oh no, no â it goes straight for several gigabytes đ So youâre just sitting there, wondering why your system suddenly starts lagging, why the audio sounds like a corrupted Star Trek transmission after a virus attack đđ You open Task Manager, sort by RAM usage⌠And there it is, grinning at you, Audio Graph Isolation, quietly turning your system into its personal victim đ How to deal with it until Microsoft finally fixes this regression? Honestly â the only thing that works is: đ forceâkilling Audio Graph Isolation in Task Manager And boom, your system instantly gets its speed back. Unfortunately, because of this regression, you have to keep an eye on this process regularly, since the RAM leak can happen anytime during idle â whether youâre watching a movie, listening to music, or the system is just running with no user input.Media Player theme bugged
Noticed that the past couple of Dev builds have a broken media player where the theme is all black and it also looks like the layout is bugged, see screenshot below. I've also submitted feedback with a screen recording but wanted to see if anyone else was experiencing this.
Azure Tiles Not loading with MS Edge Beta v147.0.3912.16
In the latest version of MS Edge, we cannot view or access the SAML Certificate data for Enterprise Applications hosted in Entra ID. Before: (v146.0.3856.62) After updating to v147.0.3912.16: As can be seen, the certificates cannot be displayed or accessed from this tile. This is affecting our test users who cannot rotate their SAML certificates but may have other impact for other Azure resources being accessed with MS Edge Beta.
o3-mini not returning reasoning tokens
Hi, I work on a service that leverages o3-mini via Microsoft Foundry. In the past few days, I've observed that when calling o3-mini via Microsoft Foundry, that completion_token_details always has the reasoning_tokens value set to 0, regardless of the reasoning setting being used. In my testing, it seems that the reasoning is still occurring, as increasing reasoning value causes the completion_tokens field to increase by a good amount, but none of the reasoning levels cause the reasoning_tokens value to be anything other than 0. Has anyone else encountered this issue? Thanks! Tom
Microsoft Managed Home Screen: Unwanted Samsung One UI 8.0 Elements Appearing
Hello Tech Community, Our organization is currently deploying a configuration in Microsoft Intune using a Corporate-owned dedicated device enrollment profile. Weâve applied a device restriction policy to configure Samsung tablets in Multi-app Kiosk mode, with Managed Home Screen set as the launcher. Instead of using an app configuration policy, Managed Home Screen is configured through the device restrictions policy. Weâve left the device navigation options unconfigured, which should hide the following UI elements: Android Overview button Android Home button Android App drawer Once all policies and required apps are installed, Managed Home Screen successfully acts as the launcher for end-users to sign in. Overall, this works well; however, weâve encountered an intermittent issue: After multiple lock/unlock cycles, the navigation bar sometimes reappears, showing the Overview, Home, and App Drawer buttons. This allows users to access background apps that are not exposed through Managed Home Screen, which defeats the kiosk experience. Device details: Samsung Galaxy Tab S10 FE Android 16, One UI 8.0 Managed Home Screen version: 2.2.0.107721 Has anyone experienced this behavior or have recommendations to prevent these UI elements from reappearing? Iâll gladly provide additional details about our configuration if needed. Thank you!New policy implementation and web enrollment for Android personally owned work profile
Weâre happy to announce two improvements for the management of Android personally owned work profile devices with Microsoft Intune, which will be available in the first quarter of calendar year 2026. A new implementation for how Intune delivers policies to devices Web based enrollment These updates modernize how Microsoft Intune manages devices and improves the enrollment flow. Action may be required by you as we move to the new implementation. Keep reading to understand whatâs changing, actions, and timelines you need to know. Whatâs changing New implementation Weâre finalizing our work on moving the Android personally owned work profile implementation to the latest and greatest available â Googleâs Android Management API (AMAPI). It has been almost a decade since Intune released support for Android personally owned work profile management. At that time, we accomplished this by building a custom device policy controller (DPC), in the form of the Intune Company Portal app. A lot has changed since then. Google released AMAPI and its companion app, Android Device Policy, which enforces AMAPI policy on devices. This is now Googleâs recommended implementation, which we used to deliver the three corporate Android Enterprise management methods: corporate owned work profile, fully managed, and dedicated. Google no longer recommends use of custom DPCs and theyâre deprecating associated functionality. The benefits of moving personally owned work profile management to AMAPI include: Faster release of new features across all four Android Enterprise management options. Consistent behaviors across all four Android Enterprise management options. The Microsoft Intune app will replace the Company Portal app as the user app (to manage devices, contact their IT department, collect logs, and more), providing an updated user experience and aligning it with the corporate Android Enterprise management options. Enables Intune to support the latest Android platform management capabilities, which are unavailable with custom DPC implementations. Web based enrollment The move to AMAPI also enables us to build a web-based enrollment flow for personally owned work profile devices, similar to web based device enrollment for iOS. The benefits of this include: Users donât need to manually install an app to start Intune enrollment since they can start enrollment from a webpage instead. Users can access enrollment from any of the three different entry points which all launch the same webpage: A URL (new!) Productivity appsâŻ(whenâŻadmin has configured conditional access so that theâŻuser isâŻrequired to enroll before accessingâŻcorporate resources) The Company Portal app This gives you more options for how to guide your users to get set up. 3. Android enrollment is more consistent with the iOS web-based enrollment flow. How to configure and monitor Web based enrollment We will release a new setting that will allow you to switch your tenant to the new web-based enrollment for all personally owned work profile enrollments going forward. We recommend that you configure this in a test tenant first, try out and document the user flow, and prepare your helpdesks accordingly before opting in on your main tenant. Once you opt in, there isnât an option to opt out. Later on, weâll automatically configure all personally owned work profile enrollments across all tenants to be web enrollments. New implementation Weâll release a new configuration policy thatâŻallowsâŻyou to migrate device groups to the new implementation. As a best practice, we encourage admins to evaluate migrating a smaller device set before migrating all devices. âŻBefore moving devices to the new implementation, you may want to email users orâŻconfigure custom notificationsâŻto inform them of what to expect.âŻâŻ Later on, Intune will automatically migrate all remaining devicesâŻusingâŻthe custom DPC implementation over to the new AMAPI implementation. Monitoring Thereâll be a new report that will show how many personally owned work profile devices are in each of the following states: On AMAPI Not targeted to move to AMAPI Targeted to move and pending completion (since it may roll out over some time) Attempted to move and hit an error (and why) How this will affect your users Web based enrollment After you opt in to web based enrollment or later after itâs changed to the default, all devices (on all Android OS versions) will enroll with the web based flow. These devices will be managed with AMAPI. After enrollment, Intune will install a few apps automatically to ensure streamlined management. Microsoft Intune: User-facing app to manage devices, contact the IT department, collect diagnostic logs, and more. Company Portal: For mobile app management (MAM). Android Device Policy: To enforce AMAPI policies. This app is installed in a âhiddenâ state, so users won't see it in their app list. Microsoft Authenticator: To provide single sign on for usersâ work account. Below is an example of the web based enrollment flow that a user would see if they needed to set a PIN on their device to meet admin requirements. New implementation When a device is moved to the new implementation (either through admin configuration or the later automatic move), devices wonât unenroll and users wonât lose access to corporate resources. Moving enrolled devices to the new implementation will be supported on any device running supported Android OS versions for user-based management methods at that time. The changes on the device will be: The Microsoft Intune app will install, and it will be the app for users to interact with instead the Company Portal. Users will not see a notification about this app installing. The Android Device Policy app will install to enforce policies. Users will not see a notification about this app installing and it will be in a âhiddenâ state on their device. If a device connected to corporate Wi-Fi with username and password authentication, when they move to AMAPI, they will lose access to corporate Wi-Fi until they sign in to the corporate Wi-Fi again. To avoid any potential disruption, we encourage you to move to certificate Wi-Fi authentication instead (as mentioned below). Timeline We'll update these timelines to provide more specific timeframes in the coming months. 2025:âŻUse this time to revise any relevant policy configurations, update your internal documentation, and prepare your helpdesk teams, as advised below. First quarter of calendar year 2026: Enrollment: Youâll be able to opt in for all enrollments of personally owned work profile devices to be web based enrollments on AMAPI. New implementation: Youâll be able to set a configuration policy to migrate groups of previously enrolled devices over to AMAPI. Later on: Enrollment: All enrollments (regardless of past configuration) will be web enrollments for devices running all Android OS versions. New implementation: All devices still on the custom DPC implementation and running supported Android OS versions for user-based management methods at that time will be automatically moved over to AM API. You will receive advanced notice of when these changes will be applying to your tenant. How to prepare We recommend you make these changes to prepare for the upcoming release and provide the most streamlined experience for users. Replace custom policies:âŻIntune ended support for custom configuration polices for personally owned work profile devices in April 2025. Custom policies are not supported in the new implementation. Replace all custom policies with equivalent policiesâŻusing thisâŻsetting mapping. Certificate authentication for Wi-Fi: If youâre using username and password authentication for Wi-Fi policies, we strongly encourage you to move to certificate authentication instead. Devices that are connected to corporate Wi-Fi with username and password authentication will lose access to corporate Wi-Fi when they are moved to AMAPI until the user signs into the corporate Wi-Fi network again. Devices using certificate authentication for Wi-Fi wonât lose access, and itâs also a more secure authentication method. Evaluate biometric configuration: Devices on the new implementation won't apply policies that prevent users from using face, fingerprint, iris, or trust agents to unlock their device. However, policies that prevent this at the work profile level are still supported. If you have this configured at the device level, consider blocking at the work profile level to protect work resources in an equivalent way. Note that for users who have turned on the setting to use one lock (unified password for the device and work profiles), then biometric settings configured for the work profile will apply to the device instead, since there isn't a separate work profile unlock. Review enrollment restrictions: In enrollment restrictions (also referred to as device platform restrictions) the âAndroid Enterprise (work profile)â restriction for personally owned work profile devices has a setting to Allow or Block âPersonally ownedâ devices. This configuration will not apply to devices on AMAPI and the setting will be removed from the Intune admin center when all devices are moved to AMAPI. As communicated in the Intune Android 12 blog, this setting does not work reliably on devices running Android 12 and later. Conceptually, personally owned work profile management is meant for personal devices, so blocking personal devices from enrolling and only allowing corporate devices isnât recommended. If you currently have the âPersonally ownedâ setting set to Block for personal work profile devices, you should plan an alternate way for blocking these devices. Options include using a corporate management method instead (such as corporate owned work profile) or configuring the personal work profile enrollment restriction to block enrollments for all users except for users in a specified group. Update Android OS: Intune currently supports Android 10 and later on personally owned work profile devices. We recommend you guide users to update to their deviceâs latest supported Android version for the best experience. Helpdesk preparation: Inform your helpdesk teams of these coming changes so they know what to expect. For devices on the new implementation, diagnostic logs will be collected using the Microsoft Intune app (instead of the Company Portal app). Plan to update any user instructions you have after you try out the web based enrollment flow. iOS web based enrollment:âŻWe recommend you consider setting upâŻweb based device enrollment for iOSâŻnow or whenâŻwe releaseâŻAndroid web based enrollmentâŻfor a more consistent and improved user experience. Changes to be aware of A few defaults will change as part of the move to the new implementation. Required app installation behavior: In the custom DPC implementation, users can uninstall required apps, and then they are reinstalled automatically within a few hours. In the new implementation, users wonât be able to uninstall required apps from their device, which is the same experience as on corporate Android Enterprise devices. Caller ID and contact search: In the custom DPC implementation, the settings to âDisplay work contact caller-id in personal profileâ and âSearch work contacts from personal profileâ are two independent settings. In AMAPI, they are controlled with a single setting. If you have blocked either, Intune will automatically block both for devices on the new implementation. Intune will update the policy user interface to have a single setting once all devices are on the new implementation. Screen timeout: In the custom DPC implementation, you can configure screen timeouts either for the full device or for the work profile under âMaximum minutes of inactivity until work profile locks.â In AMAPI, you can only configure this at the work profile level. Intune will set this to the lesser of the two when devices move to the new implementation. We will remove the device level setting from policies when all devices are on AMAPI. Security provider and Google Play services: The compliance settings for "Up-to-date security provider" and "Google Play Services is configured" won't be supported for devices on AMAPI. This is because security providers will automatically be updated and Google Play Services are required for device enrollment and management. Intune will remove these settings from compliance policies when all devices are on AMAPI. Password:âŻThere will be some minor changes to how some configurations of password requirements apply on some devices. We will update to provide more information and guidance. Enrollment reports: A couple of enrollment reports will not report on devices enrolled into AMAPI management. They are the âEnrollment failuresâ and âIncomplete user enrollmentsâ reports that are found in Devices > Enrollment in the Monitor tab. Google Domain allow listing: The device restriction setting âGoogle domain allow-listâ will not be supported for devices on AMAPI. This capability is now managed directly in the Google Admin console rather than through device restriction policies. Once the onboarding account has been migrated to a Microsoft Entra account and federated with a Google account, admins can configure this setting in the Google Admin console under the Third-party integrations node by enabling âAuthenticate Using Google.â Intune will remove this setting from device restriction policies once all devices are on AMAPI. Stay tuned to this blog for updates! If you have any questions or feedback on this change, leave a comment on this post or reach out on XâŻ@IntuneSuppTeam. Post updates 02/19/25: Updated the Timeline and How this will affect your users + New Implementations sections. 04/08/25: Updated these sections: How to configure and monitor, How this will affect your users, Timeline, How to prepare, and Changes to be aware of. 04/09/25: Updated the Changes to be aware of section to include details about TeamViewer supportability. 08/22/25: Added images and updated all sections with the latest information, including an updated Timeline section and removing the information about the delay to TeamViewer support. 09/09/25: Added a screenshot to clarify Android enrollment restrictions. 09/23/25: Update the Changes to be aware of section to include more information about 'Enrollment reports'. 02/12/26: Updates to the Changes to be aware of section to include more information about 'Security provider and Google Play services'. 03/27/26: Updates to the Changes to be aware of section to include more information about 'Google Domain allow listing'.The New Activation Portal Is Partly Broken But It Is a MAJOR Inconvenience For Me & Others.
I Run Windows 7 Ultimate x64 And I need to Activate Windows, I am used to the new aka.ms/aoh replacing the phone line. But I Have Activated Windows XP & Vista Without Any Problems Multiple Times, I Tested It Too, Tried 7, Starter, Home, Pro, Ultimate, Even x32 & x64. Though, No matter what, everything BUT Windows 7 Works. This Is Clearly a Server Sided Issue And I've Had This problem for the past months maybe even about a year. (The Product Key I Am Using Is Not Public on The Internet So It's Not Blocked/Used Publicly By Everyone, it is the same product key that came with the CD) And I Can Say For Certain This is a Server Sided Issue. Please Help. And Thank You For Your Time..NET
Hi everyone! đ Iâm new to this community and currently learning .NET App Development. Iâm really excited to join and connect with developers here. I believe the discussions and knowledge shared in this community are very valuable, especially for beginners like me. Iâm looking forward to learning from your experiences and improving my development skills. If you have any tips, recommended resources, or advice for someone starting with .NET, I would really appreciate it. Happy to be part of this community! đ
