Yes - sounds the same and this is 10.2.300.4 (fails on all 10.2.300.xx releases) and the interesting part is that 10.2.200 works (which kind of rules out the CRL check). The sad part is if you have Internet up/downs or longer slow periods you WILL notice it in application performance.
Maybe we can log and find out what its sending/receiving on the net . How to Track Internet Activity for Free Using Windows Firewall Log - Make Tech Easier
Update - oh i see you logged Azure traffic
Yep - Between a ProcMon dump and Wireshark I have plenty to comb through 
So, if we know what were looking for, with a little luck maybe we can identify the offending methods and make it easier for Epicor to fix it
I am on that path right now and hope to come up with something tonight.
Well - I did not fully solve but am able to get around this. The slowness seems related to the use of Brightcove and it looks like it is integrated into each menu item (except a few) for something help related. To test I added a host entry on the server for 127.0.0.1 edge.api.brightcove.com and BAM the speed was back.
@aidacra @Bart_Elia - any additional insight? Can we disable this elsewhere?
And I was just about to ask if you were opt’d out of telemetery.
Telemetry a long time ago does not have any impact on whatever this is doing.I even shut down Windows telemetry.
I just hate you are working on this on a Saturday night, unless you are having a blast that is. I looked up the brightcove and it was a little curious. Seems related to video but I just couldnt make any link to what it would be used for in Epicor. Especially in every menu item. I havent stayed in the loop much on the Kinetic stuff, has it been working its way into the release version? I only ask because I saw some mention of similiar auth problems with a connector - which kinda made me think about Kinetic
Is Brightcove the video provider for Epicor’s e-learning?
Yes - they are all the video behind the new active homepage and the Knowledge On Demand
Great troubleshooting! I have no idea if there is a simple way to disable these calls 
I’m finding out.
@danbedwards - Thanks for the detail. Work around worked for me as well. Following this thread to see what the permanent fix will be.
@aidacra is pushing on the issue in the new Knowledge On Demand functionality.
For those reading along at home, the Telemetry system is built on the same framework as the tracing subsystem. It pushes data to a background queue and let’s the client go about its day. In a background task the queue is flushed to disk for trace, to cloud for telemetry. This risks losing a few ms of data but the benefit of not being a blocking, synchronous call is worth it.
Nathan might reach out if you don’t already have a ticket.
This is related to feature added in 300 to provide context-sensitive video help to forms. There are about 5 forms that use it now, but yes the call to see if videos exist on a form is in a base form layer. Try customer maintenance to see it work functionally. On Customer Maintenance go to Help > Video Help.
Issue has been entered and I’ll report back here soon.
Basically the code executes a call to Brightcove REST API (our video hosting partner) that says “are there playlists for this form” The call does use a c# dynamic object which bears looking into as a performance issue.
We haven’t noticed the performance hit in-house and I wonder if the Brightcove URL is blacklisted on your network Dan?
Regardless, we’ll look at the issue, check about externalizing the URL (to make it visible to be whitelisted), and/or add flag to enable/disable feature.
and thanks Dan for providing the work around!
Oh sorry I didn’t read far enough back into thread. Seems like the fix might be to set a (new?) global flag on a background thread when Epicor is launched to indicate internet access status. Forms or whatever could subscribe to the flag before running code that seeks responses from internet.
That seems like a beautiful solution. Thanks to all the Epicor folks here helping us out!
Tied to Software Change Request ERPS-104047 targeted to be addressed in 10.2.300.7 (available December 19th).
Link to KB article created with more context and a couple of workarounds, already discussed in this thread.
KB0043813