Anonymous
My feedback
-
28 votesstarted · 5 comments · Azure Active Directory » Conditional Access · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
39 votes5 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Anonymous
supported this idea
·
-
5,892 votes
DNSSEC remains on our long term roadmap, however it is unlikely to be available in CY 2019. If DNSSEC is a critical and immediate requirement for your business we’d suggest that you consider evaluating 3rd party DNS hosting solutions that provide this feature.
An error occurred while saving the comment Anonymous
commented
#1 case,
We have experienced issues regarding our DKIM signing. Our email was spoofed because the receiving party was infected. They than signed the email with there own DKIM keys and our email was incorrectly all flagged as spam. This is because they were able to manipulate our DNS systems.#2 case,
Manipulation of the DNS website records. Website records that were hijacked. This increases the risk for our customers.#3 case,
for banking purposes we absolutely require the use of DNSSEC. It is a requirement from our regulator.Anonymous
shared this idea
·
Currently the on-premises Azure MFA (on ADFS) pinmode does exactly what we need.
I would be great if this functionality becomes available in azuread cloud-only.