■Description:
We would inform you that there are customers who are using the environment with MDM Office 365 and Intune in parallel.

Originally, it is not preferred to use the security group to multiple MDM Authority.
Despite it, some of the customers have used the security groups to enroll in MDM Office 365 policy enrollment destination by applying Intune policies that had been used before.
As a result, the unexpected behavior happened then the security group got damaged eventually.

To prevent the fraudulent use of security groups using multiple MDM Authority, we hope the feature will be added that allows restricting for the users of security groups using different MDM authority on the system side , or making alerts at the time of setting in both of the Office 365 admin portal and the Azure portal.

I am missing the ability to automatically identify the owner of the device during enrollment. It is most likely that the person enrolling the device is the actual owner of the device. The users have to go through a lot of steps to enroll their phones. To install apps from the company portal a user needs to be identified on the device. When this do not happen automatically, the user need to go through even more steps to install apps. I opened a ticked with Microsoft, but the case got resolved with the following note : This is by Design working as expected ,need to select the device manually first once enrollment completed, then only able to install Apps available in Company portal.

■Description:
For security reasons, some organizations need to locate the Wi-Fi administrator and the administrator of Device Configuration profiles separately. For that reason, the global administrator does not want to inform the Wi-Fi password to the administrator of the Device Configuration profile.

In Intune, we are requiring to upload the ". xml file" in order to deploy the custom Wi-Fi profiles. It is problematic from a security point of view because it can be confirmed the uploaded Wi-Fi password when the administrator of the Device Configuration profile accesses to the existed Profile blade on Azure portal.

Therefore, I would like you to implement the option that allows the file uploaded to Azure portal masked by GUI. We believe that this will help so many customers now and in the future.

Thank you for your consideration,

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 AzureAD joined - maybe store it just like bitlocker key as attribute of the device in AzureAD when CompanyPortal is installed.

2) Allow configuring the behavior of if/when to generate device ID as a setting of Company Portal in the Store4Business private store. Then store current computerName+DeviceID in Microsoft Store Business.

3) Have MDM CSP or OMA-URI to control when/if to generate DeviceID and record/report the deviceID into "Windows Analytics Upgrade Readiness" maybe as part of "Additional Insights" like the site-discovery and Office add-in discovery, have an "AutoPilot ready" section.

PROBLEM STATEMENT:

How to disable the Windows 10 Express File

WORKAROUND ANALYSIS:

What we did here is to disable the Windows 10 express file settings. But the previous downloaded updates when the settings still enabled still the download the express because as per MS Premiere it was already save in DB and could not clear it.

I have to download the latest one where the express is not enable, then the files being downloaded is back to normal without the express files.

IMPACT TO BUSINESS:

The affected here are the Storage and network bandwidth because the files is too big and some of the sites with smaller BW could not download the express files.

COST IMPACT:

since the express files size are too large we have to increase the storage device and there is corresponding cost in our environment every time that we need to extend the drive capacity. On the business side we have to expand the BW so the express files will distribute to corresponding DP’s/