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. Ability to deploy with Intune autopilot in self deploying mode to Azure AD Hybrid

    Now, when you select "Self Deploying" the "Hybrid" drop down goes away. We'd like to do self-deploying + Hybrid at the same time.

    40 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 →
  2. Windows Enrollment restriction and Corporate Device Identifiers

    A lot of customers have O365 and their users like to use O365Pro Plus or configure their mail account at home on their personal devices. With that they are asked to add the Account as "Work or School Account", which registers their personal devices automatically in Azure AD. That is ok, but if the customer then buyes EMS licenses and assign them to user, all the devices are enrolled to Intune. Even more worse is, that with that you will no longer be able to target anything to users. Because if you for example would like to deploy Windows 10…

    25 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 →
  3. Azure hybrid domain join with remote user login

    I would like to be able to deploy new computers to remote users with Azure hybrid domain join. Currently this isn't possible because after the hybrid domain join process runs, the user can't login to the computer because the (local) domain is unavailable. If you could cache the 1st time login, it would circumvent this issue.

    23 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 →
  4. AutoPilot OOBE Enrollment separate language and region setting

    Please allow separate language settings for Windows AutoPilot OOBE.
    One for display language,
    and one for region.

    We have a multilingual company. Where we set OS-display-language to English US and Region settings to Dutch.

    22 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 →
  5. Support for Federated Domains with Windows Autopilot

    At present when using Windows Autopilot, a user on a federated domain is unable to sign in to complete the set up. However domains that aren't federated are supported. With this in mind, please can support be added for Federated domains within Windows Autopilot?

    This feature would be incredibly useful in enterprise environements, where Hybrid Azure AD isn't an option.

    21 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 →
  6. 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 →
  7. 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 →
  8. Allowing DEM support for Autopilot

    Currently you are unable to use the DEM account with Autopilot devices. Annoyingly as a IT admin you don't want your own account as the user who enrolled the device into Intune. Currently the only way to enroll the device as a end user is to know their login credentials.

    19 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 →
  9. Allow Auto Pilot to set computer names

    Any machine enrolled though Auto Pilot has a random computer name assigned. If a machine is Factory reset and reenrolled via Auto Pilot, the machine name is lost.

    Auto Pilot should firstly persist computer names, but also we should be able to define a rule to allow custom naming, as well as manually define computer names for when machines are enrolled. For example:
    If Type=Surface Pro, then Name=SP<serialno>

    18 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 →
  10. Customise AutoPilot screen (Company Branding)

    When Azure's Company Branding is configured, there should be an option to customise the "Enter your %organisation's% email." message.

    Our organisation enrols with a UPN as opposed to email address, so this could confuse our users. Please refer to screenshot for the exact section.

    17 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. Notification when a new device is Azure AD Joined / registered

    When allowing users to enrol / join their own devices, generate an email notification to be sent out, either to a specific person / group or to the user populated in the Manager attribute.

    If additional business processes are required after a user registers a device, currently there is no convenient way for anyone to be notified.

    Rough flow would be;
    Manager A issues new device to User A.

    User A configures the device at home with AutoPilot.

    Upon Azure AD registration an email is sent to Manager A letting them know that User A has configured Device A.
    Manager…

    16 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 →
  12. Add already joined devices to autopilot for reimaging

    It would be nice to be able to add already joined devices into Autopilot program (like a writeback or sync) for re imaging purposes. This would make re-purposing hardware simple and easy for users and admins alike.

    I cannot gather the hardware ids through AzureAD (cloud only) with no WMI capabilities and limited AAD attributes being available.

    16 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 →

    As of the release the week of Oct 1, 2018, 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? If not, what’s missing?

  13. Autopilot Selfdeploying with Hybrid Azure AD Join (local domain join)

    I would like to use the Autopilot Selfdeploying function with Hybrid Azure AD Join to also join the local domain. This would really help us since we are using flexible work spaces (desktops that get's used by different users on a daily basis).

    15 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 →
  14. 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 →
  15. Add Multifactor Unlock configuration to WHfB Windows enrollment options, Security Baseline and CSP.

    Our Info Sec team won't allow PINs for WHfB unless we use Multifactor Unlock. Currently this cannot be configured in Intune except perhaps by an ADMX backed custom CSP. This needs to be added to the WHfB configuration pages for Windows Enrollment, the Security Baseline and Identity Protection Profile type in Device configuration profiles.

    Here is the documentation on the GPO that needs to be translated. https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/feature-multifactor-unlock#create-the-multifactor-unlock-group-policy-object

    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 →
  16. 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 →
  17. 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 →
  18. Require patching to complete before AutoPilot completes provisioning device

    For the longest time we've been able to ensure that the device is fully patched after imaging but with AutoPilot there is a significant delay after provisioning until Windows Update tries to evaluate the patch compliance of the device. This is a big feature for security admins when allowing devices on the corporate LAN and I wonder how this would work for people who use device health because the machine is not fully patched after provisioning.

    I'd like to see a setting for AutoPilot to pause the provisioning process until the device has installed its patches. The device would be…

    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 →
  19. 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 →
  20. Support B2B/Guest identities within Intune and Autopilot

    Add in support for using B2B/Guest accounts from another tenancy within Intune and also Autopilot. Currently, if I invite an identity from another tenacy and then take that identity through Autopilot, it fails with "Something went wrong. That username looks like it belongs to another organisation. Try signing in again or start again with a different account". I've read that Intune doesn't support B2B/Guest identities. Please support B2B/Guest identities for Intune and Autopilot.

    Thanks

    10 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 →
  • Don't see your idea?

Feedback and Knowledge Base