Home
%3CLINGO-SUB%20id%3D%22lingo-sub-266577%22%20slang%3D%22en-US%22%3EWindows%20Analytics%20has%20moved%20to%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266577%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Azure%20Log%20Analytics%20team%20has%20announced%20%3CA%20href%3D%22https%3A%2F%2Fna01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fazure%252Flog-analytics%252Flog-analytics-oms-portal-transition%253Ftoc%253D%252Fazure%252Fazure-monitor%252Ftoc.json%26amp%3Bdata%3D04%257C01%257Cmarcshep%2540microsoft.com%257Cfab07a098afb4a77c18c08d628b92198%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C636741172925619790%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%253D%253D%257C-1%26amp%3Bsdata%3DP4a1Tojm7dgsEgxIJPKYlxsMDWTnMhoNSOYZwMji13c%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethe%20OMS%20classic%20portal%20is%20being%20replaced%20with%20Azure%3C%2FA%3E%20and%20will%20be%20shut%20down%20entirely%20in%20January.%20The%20Windows%20Analytics%20team%20has%20recently%20completed%20the%20work%20to%20port%20our%20solutions%20to%20Azure%2C%20and%20created%20documentation%20for%20using%20%3CA%20href%3D%22https%3A%2F%2Fna01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fwindows%252Fdeployment%252Fupdate%252Fwindows-analytics-azure-portal%26amp%3Bdata%3D04%257C01%257Cmarcshep%2540microsoft.com%257Cfab07a098afb4a77c18c08d628b92198%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C636741172925629795%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%253D%253D%257C-1%26amp%3Bsdata%3DJk9%252Bcv7BjVjSjxaLu46HkQP1XjReB%252Fa3oPd5vQjGn5Q%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EWindows%20Analytics%20in%20the%20Azure%20portal%3C%2FA%3E%20describing%20the%20steps%20current%20customers%20will%20need%20to%20take%20to%20manage%20the%20transition%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EAdditional%20permissions%20that%20must%20be%20set%20to%20allow%20continued%20access.%3C%2FLI%3E%0A%3CLI%3EWhere%20to%20find%20a%20small%20handful%20of%20experiences%20that%20have%20a%20new%20location%20in%20Azure.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EWe%E2%80%99d%20like%20to%20encourage%20all%20our%20customers%20to%20make%20this%20transition%20now.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3EThe%20Windows%20Analytics%20team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-293145%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Analytics%20has%20moved%20to%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293145%22%20slang%3D%22en-US%22%3E%3CP%3EMarc%2C%20for%20some%20reason%20I%20didn't%20get%20notified%20about%20your%20reply.%20I%20will%20email%20you%20some%20screenshots.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegarding%20deployment%20script%20vs%20MDM%20URI%20-%20this%20may%20be%20your%20recommended%20way%2C%20but%20unless%20Microsoft%20is%20going%20to%20%3CSTRONG%3Edigitally%20sign%3C%2FSTRONG%3E%20the%20script%20through%20a%20trusted%20chain%20and%20update%20it%20through%20windows%20update%20I%20don't%20see%20most%20of%20my%20small%20customers%20doing%20this.%20%26nbsp%3BI%20deal%20with%20a%20lot%20of%20low%20touch%20environments%20and%20running%20unsigned%20scripts%20aren't%20allowed%20and%20most%20clients%20don't%20run%20a%20private%20PKI%20much%20less%20one%20that%20is%20exposed%20to%20roaming%20clients%20or%20internet%20only%20offices.%20The%20main%20selling%20point%20for%20Intune%20and%20M365-E5%20is%20to%20improve%20the%20security%20and%20reliability%20of%20these%20kinds%20of%20deployments.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20used%20the%20script%20for%20early%20testing%2Fsmall-pilot%20but%20not%20for%20production.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278540%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Analytics%20has%20moved%20to%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278540%22%20slang%3D%22en-US%22%3E%3CP%3ERegarding%20permissions%3A%20I'd%20need%20to%20see%20detailed%20screenshots%20to%20help%20you%20tshoot%20the%20issue.%20Please%20shoot%20an%20email%20to%20%22uasupport%40microsoft.com%22%20and%20we%20can%20help.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegarding%20lack%20of%20MDM%20policy%20to%20configure%20device%20name%20opt-in%3A%20Note%20that%20the%20deployment%20script%20(which%20is%20our%20recommended%20way%20to%20configure%20devices)%20does%20this%20automatically%20(by%20setting%20the%20preference%20key).%20So%20if%20you%20are%20using%20the%20deployment%20script%20then%20they%20should%20be%20a%20non-issue%20for%20you.%20If%20you%20are%20not%20using%20the%20deployment%20script%20(not%20recommended)%2C%20then%20yes%3B%20it's%20a%20gap%20that%20this%20can%20only%20be%20configured%20by%20GP%20and%20not%20by%20MDM.%20That's%20a%20known%20issue%20we%20plan%20to%20address%20in%20a%20future%20version%20of%20the%20product.%20I%20should%20point%20out%20that%20this%20issue%20is%20independent%20of%20the%20move%20of%20the%20admin%20portal%20to%20Azure.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-277622%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Analytics%20has%20moved%20to%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-277622%22%20slang%3D%22en-US%22%3E%3CP%3EAnother%20issue%3A%20Per%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwindows-analytics-get-started%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwindows-analytics-get-started%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20section%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwindows-analytics-get-started%23distributing-policies-at-scale%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwindows-analytics-get-started%23distributing-policies-at-scale%3C%2FA%3E)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3EAllowDeviceNameInTelemetry%20(in%20Windows%2010)%3C%2FTD%3E%3CTD%3EIn%20Windows%2010%2C%20version%201803%2C%20a%20separate%20opt-in%20is%20required%20to%20enable%20devices%20to%20continue%20to%20send%20the%20device%20name.%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20information%20does%20not%20provide%20MDM%20settings%20as%20there%20is%20no%20such%20value%20in%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fnew-in-windows-mdm-enrollment-management%23whatsnew1803%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fnew-in-windows-mdm-enrollment-management%23whatsnew1803%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20how%20exactly%20are%20we%20supposed%20to%20set%20that%20value%20through%20Intune%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20URI%20for%20this%20setting%3F%3F%3F%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276586%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Analytics%20has%20moved%20to%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276586%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20far%20the%20experience%20of%20accessing%20the%203%20windows%20analytics%20services%20through%20Azure%20Portal%20has%20been%20less%20than%20good.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20giving%20Log%20Analytics%20Contributor%20permissions%20to%20the%20correct%20account%2C%20the%20%22workspace%20summary%22%20shows%20nothing.%20However%20if%20I%20drill%20into%20%22Solutions%22%20I%20can%20see%20the%203%20solutions..%20and%20if%20I%20click%20into%26nbsp%3Bany%20of%20them%20it%20loads%20the%20page%20but%2C%20as%20an%20example%2C%20the%20%22device%20health%22%20widget%20never%20loads%20data.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdge%20on%20Windows%201803.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-266608%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Analytics%20has%20moved%20to%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266608%22%20slang%3D%22en-US%22%3EThanks!%20Will%20Upgrade%20Readiness%20be%20available%20for%20Windows%2010%20Version%201809%20soon%3F%3C%2FLINGO-BODY%3E
Microsoft

The Azure Log Analytics team has announced the OMS classic portal is being replaced with Azure and will be shut down entirely in January. The Windows Analytics team has recently completed the work to port our solutions to Azure, and created documentation for using Windows Analytics in the Azure portal describing the steps current customers will need to take to manage the transition;

  • Additional permissions that must be set to allow continued access.
  • Where to find a small handful of experiences that have a new location in Azure.

We’d like to encourage all our customers to make this transition now.

 

Thanks,

The Windows Analytics team

5 Comments
Frequent Contributor
Thanks! Will Upgrade Readiness be available for Windows 10 Version 1809 soon?
Occasional Contributor

So far the experience of accessing the 3 windows analytics services through Azure Portal has been less than good.

 

After giving Log Analytics Contributor permissions to the correct account, the "workspace summary" shows nothing. However if I drill into "Solutions" I can see the 3 solutions.. and if I click into any of them it loads the page but, as an example, the "device health" widget never loads data.

 

Edge on Windows 1803.

Occasional Contributor

Another issue: Per https://docs.microsoft.com/en-us/windows/deployment/update/windows-analytics-get-started

 

In the section (https://docs.microsoft.com/en-us/windows/deployment/update/windows-analytics-get-started#distributin...)

 

AllowDeviceNameInTelemetry (in Windows 10)In Windows 10, version 1803, a separate opt-in is required to enable devices to continue to send the device name.

 

 

This information does not provide MDM settings as there is no such value in https://docs.microsoft.com/en-us/windows/client-management/mdm/new-in-windows-mdm-enrollment-managem...

 

So how exactly are we supposed to set that value through Intune?

 

What is the URI for this setting??????

 

Microsoft

Regarding permissions: I'd need to see detailed screenshots to help you tshoot the issue. Please shoot an email to "uasupport@microsoft.com" and we can help.

 

Regarding lack of MDM policy to configure device name opt-in: Note that the deployment script (which is our recommended way to configure devices) does this automatically (by setting the preference key). So if you are using the deployment script then they should be a non-issue for you. If you are not using the deployment script (not recommended), then yes; it's a gap that this can only be configured by GP and not by MDM. That's a known issue we plan to address in a future version of the product. I should point out that this issue is independent of the move of the admin portal to Azure.

Occasional Contributor

Marc, for some reason I didn't get notified about your reply. I will email you some screenshots.

 

Regarding deployment script vs MDM URI - this may be your recommended way, but unless Microsoft is going to digitally sign the script through a trusted chain and update it through windows update I don't see most of my small customers doing this.  I deal with a lot of low touch environments and running unsigned scripts aren't allowed and most clients don't run a private PKI much less one that is exposed to roaming clients or internet only offices. The main selling point for Intune and M365-E5 is to improve the security and reliability of these kinds of deployments.

 

I used the script for early testing/small-pilot but not for production.