Microsoft

Microsoft Endpoint Manager Intune Feedback

Suggestion box powered by UserVoice

Ideas

What features would you like to see?

All of the feedback that you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Microsoft Endpoint Manager Intune, though we can’t promise to reply to all posts.

Standard Disclaimer – our lawyers made us put this here ;-) We have partnered with UserVoice, a third-party service, so you can give us feedback. Please note that the Intune feedback site is moderated and is a voluntary participation-based project. Please send only feature suggestions and ideas to improve Intune. Do not send any novel or patentable ideas, copyrighted materials, samples or demos. Your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms.


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. More options for local user account creation properties in provisioning packages

    When creating local user accounts with Image and Configuration Designer Provisioning packages there are no options to configure the accounts, such as password expiry.
    The kiosk provisioning package option allows for local user account creation however after 42 days the accounts expire. This is an issue where devices have auto-login enabled and arent managed by Active Directory.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Automatically Assign AutoPilot Profile to New Devices

    It would be great if we could assign a default AutoPilot profile that is automatically assigned to all newly imported / registered devices.

    So that a device does not have to be manully managed in Intune ( profile assignment ) before the user starts it up.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add customer tags to Autopilot device information

    I am thinking of a generic feature that would let us implement some missing features in Intune.

    A customer should be able to add a list of tags to the Autopilot device information in Intune (see screenshot)

    As soon as an AAD object is created durin enrollment these tags should be copied as an attribute that can be used in dynamic device queries. I am thinking of something like
    tag = 'SoftwareXYRing0'
    That way we would be able to add a device automatically to a group without having to code some automation script which causes maintenance costs and…

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Make it possible to Azure AD join/synchronize device (computer) objects to multiple Azure AD tenants from a single forest AD.

    Some companies hosts multiple sub-customers in a single forest Active Directory.
    Each sub-customers users and machine objects are organized in their own OUs.
    Present configuration would be one AAD Connect server per customer OU – which synchronize the user objects to their respective individual Azure Tenants and they license all their sub-customers AAD Users with M365 licenses.

    Some would like to enable Automatic AAD Join (Hybrid Azure AD Join) for their sub-customers Windows 10 Enterprise devices via GPO.
    They want to manage the sub-customers domain-joined devices with Intune, and use device-based conditional access.

    AAD Device Registration (DRS) requires a Service…

    206 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow EES subscriptions to use autopliot

    We have been told that we cannot use autopilot with our EES agreement as it only works with CSPs.

    This is of no use to many educational organisations.

    Do you have plans to allow autopilot with EES licences?

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Discontinue all development of Intune

    I cant believe in the year 2018, that Microsoft is still using a dead technology called Silverlight as a cloud management platform for its customers end device management. I am almost ashamed to tell other IT administrators I have a client who depends on Intune as the first line of defense on all Computers and Tablets.

    There is a great tale out there that migrating to Azure will vastly improve the product. I don't believe this fairy tale.

    My suggestion, is to simply build all the functions that Intune is capable of and provide them directly from the Azure portal.…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  7. Initial Azure AD Join with user rights, without asking a local Admin elevation privileges

    hello,

    During the initial Azure AD Join, if the user has no local admin rights he is asked for an elevation of privilèges.
    Is it possible to change this in order for users to join the Azure AD domain without admin rights ?

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Assign Intune device category through Autopilot

    It would be great if we could assign Intune device category through Autopilot, without having to do it manually once the device is enrolled.

    53 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  9. AutoPilot: Use CompanyPortal app to push/collect DeviceID data for already deployed Win10 computers

    One of the biggest problems with AutoPilot is getting the deviceID info from existing devices that are only cloud managed.

    It would be helpful to be able to pull DeviceID and Current Computer name from the CompanyPortal app installed on Windows 10 1703+ devices.

    Assumptions:
    MMD Management: Intune on Azure Portal (at least migrated from silverlight) (Intune or EMS E3+ for license)
    Authentication: Azure AD Joined with at least a P1 AzureAD license assigned
    Device: Windows 10 devices that support AutoPilot (so far 1703+)
    Application: Windows Store App "Company Portal" is installed

    Possible workflows -

    1) Since the device is…

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Configuration Status & Configuration Planning

    When deploying software and configuring devices, I currently have no idea what is going on. We have been testing with AutoPilot and Intune to automatically configure laptops and install software on them, but I've no idea what is going on most of the time and I am having to use Task Manager on the devices in question to get a clue as to what is being installed and what it's status is. If there was a way of showing this in the console against each device that would be great.

    Also it would be nice to be able to apply…

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Clean start layout policy

    Today there are two options to apply a start layout to users, fully locked or partial locked.
    Fully locked start layout will clean the start layout from "consumer things" and nicely only show what have been deployed centrally. But lack support of user customizations such as pinning and resize.
    Partial locked start layout will allow the users to customize the start layout and show what have been centrally deployed, but it will also show the default start layout/"consumer things" on the desktop that are not wanted in an enterprise.
    I would like to see an option to either clean start…

    169 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  12. Register Windows AutoPilot devices direclty in the Intune Azure Portal

    Since there is a management portal for AutoPilot devices in Intune it would be great if we could register the devices directly there. Instead of using the Microsoft Store for Business and then using the sync, which is only manual at the moment.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →

    As of the October 2018 release, you can apply Autopilot profiles to enrolled Win 10 devices that have not already been registered for Autopilot. In the Autopilot profile, choose the Convert all targeted devices to Autopilot option to automatically register non-Autopilot devices with the Autopilot deployment service. Allow 48 hours for the registration to be processed. When the device is unenrolled and reset, Autopilot will provision it.

    Does that get you what you want?

  13. Create AutoPilot for Education - Bulk enrollment with SharedPC

    Need ability to purchase OEM computers that have already been Azure AD Joined as SharedPC computers using AutoPilot. Also, the ability to do this for previously purchased computers. This eliminates having to individually register and enroll each computer. Computers can then use Intune Policy to configure and manage computers and embrace Cloud-First MDM.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  14. AutoPilot - Option to use SharedPC configuration service provider

    Need the option when using AutoPilot to setup Windows 10 Shared PC mode using SharedPC configuration service provider. It's critical to use AutoPilot to bulk enroll devices as Shared PC's. This will eliminate the need to manually apply PC packages to each device for configuration. A Windows 10 PC in shared PC mode allows for computers to be management and maintenance-free with high reliability.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Restrict Intune device registration and enrollment to only Azure AD Joined computers(no Domain Joined)

    Allow Cloud based enterprises to migrate computers away from Domain Joined to Azure AD joined for modern device management. Currently cannot restrict Domain Joined computers from also Azure AD join. Need an Intune policy to control this.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Azure AD Hybrid joined Windows 10 Devices should recognize a device owner through Intune.

    Azure AD Hybrid Joined Windows 10 Devices does not list a device owner for Windows 10. This could perhaps be made available through intune. If a device is Azure AD Joined and Intune joined, then the owner in Intune could be set as device owner in Azure AD? Great if this option was available or at least if admins got to turn it on by choice.

    247 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Static computernames in Windows autopilot before Intune autoenrollment.

    Maybe posting this to the wrong component-team but a suggestion would be to give the ability to set a static computername to the imported device when registering the csv file containing hardware information in "Autopilot deployment". The current functionality randomizes the computername after each factory reset or reinstallation. Seems pointless to perform a namechange after Intune autoenrollment. This would solve alot of of administrative issues within larger organizations.

    235 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    23 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →

    As of the week of August 27, you can use a template to control how the machine will be automatically named. So not exactly static, but gets you away from total random. From the discussion, sounds like not total random was good enough for some, but not all, so I will switch this back to “noted”.

    more detail about what we released in August:
    When you create an autopilot deployment profile, you can designate a name, which must be 15 characters or less, and can contain letters, numbers, and hyphens. Names can’t be all numbers. Use the SERIAL macro to add a hardware-specific serial number. Alternatively, use the RAND:x macro to add a random string of numbers, where x equals the number of digits to add.
    https://docs.microsoft.com/en-us/intune/enrollment-autopilot#create-an-autopilot-deployment-profile

    It’s only available with the Windows Insider build for now.

  18. Set Timezone for Windows 10 from Intune MDMFollowing the "Autopilot" idea I'd like to install MSI application from Intune MDM however

    Following the "Autopilot" idea I'd like to install MSI application from Intune MDM via Azure AD joined laptop/surface however by default the Windows Auto timezone service is turned off so new users wont have applications installed from Intune MDM because the date/time on a new device does not match the MDM "as soon as possible" date/time requirements for deployment of Applications i.e. The OOTB Autopilot experience cant work for application deployment unless a new user sets the timezone correctly first!

    Thanks
    Peter

    How can I fix this

    228 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google Microsoft Intune
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Autopilot/Windows enrollment  ·  Flag idea as inappropriate…  ·  Admin →
1 2 3 4 6 Next →
  • Don't see your idea?

Feedback and Knowledge Base