@Bart Sipes Thanks for the report; please file this issue using the Feedback button for tracking.
The problem you're encountering at this time is that Edge's policies are not read from Chrome's policy location.
I am curious to learn more details of your issue, however-- What is the hostname and the CA in use? (Feel free to email me directly ericlaw@). It's unexpected that many environments will hit this issue. In most cases like this, the CA root certificate used by the enterprise is considered a "legacy" root and thus CT is not enforced. In contrast, public CAs working under the baseline requirements should be issuing with CT and will not issue to "dotless" hostnames. Rare exceptions include Microsoft (which has a CA that is both trusted by default and issues our intranet certificates).
