Chad
My feedback
-
1 voteChad
shared this idea
·
-
19 votes
An error occurred while saving the comment Chad
supported this idea
·
-
219 votesunder review · 7 comments · Networking » Content Delivery Network · Flag idea as inappropriate… · Admin →Chad
supported this idea
·
-
90 votes9 comments · Azure Monitor- Alert Management » Configuring Alerts · Flag idea as inappropriate… · Admin →
Hello,
I’m reaching out to let you know that we’ve started designing this feature.
We’re planning to conduct a usability study in the coming weeks to test this feature’s UX, and looking for participants to take part and help shape this feature.
If you’re interested in participating in this study, please reach out to me at harelbr@microsoft.com
Thanks!
Harel Broitman
Principal PM, Azure Monitor AlertsChad
supported this idea
·
-
4 votesChad
shared this idea
·
-
5 votesChad
shared this idea
·
-
4 votesChad
shared this idea
·
-
276 votes
Given that a Azure AD B2C tenant should only be used for configuring Azure AD B2C, would having programmatic API’s to configure all of the Azure AD B2C settings be useful or is there more that you are looking to achieve using ARM templates?
/Parakh
An error occurred while saving the comment Chad
commented
A start for automating the IEF data plane of B2C once you have a tenant!
https://github.com/azure-ad-b2c/Scripts/tree/master/IEFTenantSetupV2
https://github.com/Azure-Samples/ActiveDirectory-B2C-MSGraph-PolicyAndKeysets
Chad
supported this idea
·
An error occurred while saving the comment Chad
commented
Since Adam submitted this request, and now he is on the team ..... can we get an update :D
-
106 votes17 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Chad
commented
Basic security on a b2c tenant that must immediately be disabled when using automation for advanced things like OAUTH permissions granting :(
Chad
supported this idea
·
-
137 votes
An error occurred while saving the comment Chad
commented
This is a starting point via IEF: validate new PW doesn't match (current) PW. Nutty this is not available out of the box
https://github.com/azure-ad-b2c/samples/tree/master/policies/password-reset-not-last-password
Chad
supported this idea
·
-
31 votes
An error occurred while saving the comment Chad
commented
Conditional Access for B2C is in preview: https://docs.microsoft.com/en-us/azure/active-directory-b2c/conditional-access-identity-protection-setup#supported-identity-protection-risk-detections
It does mention supporting the BOT related "malware linked IP" rules from big daddy AAD CA: https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/concept-identity-protection-risks#sign-in-risk
Does not exactly seem to be CAPTCHA related though - if you want human detection consider: https://github.com/Azure-Samples/active-directory-b2c-node-sign-up-user-flow-captcha
Chad
supported this idea
·
-
2 votesChad
shared this idea
·
-
2 votesChad
supported this idea
·
-
41 votesunder review · 4 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Chad
commented
Sending alerts to O365 email groups is problematic, they generally dont get delivered for reasons unknown.
Try adding SMS provider email domains into those groups - those really dont work!
Would be nice to get some webhook functionality for teams/slack (outside of channel emails for the reasons mentioned above).
Chad
supported this idea
·
-
33 votesstarted · 1 comment · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →Chad
supported this idea
·
-
Azure B2C custom user attribute validation like using regex, range etc. e.g. postcode, date of birth
68 votesThe immediate term is to make this possible by giving you full control of the B2C provided pages (sign up, sign in, etc) by allowing custom javascript (https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/15493536-add-support-for-javascript-inside-the-custom-ui-br).
Chad
supported this idea
·
-
83 votes
We’re looking at this feedback and along with work for verification emails, looking to do some work around customization to completely remove the Microsoft brand and allow this depth in customization. Please bear with us as we are looking at how best to prioritize these changes.
/Sam
Chad
supported this idea
·
-
99 votes
This is not planned for the next 6 months. If this is needed for your scenario, please continue voting and we will re-evaluate at a later.
Chad
supported this idea
·
-
89 votes
There is a current configuration to allow users to choose to remember a device for MFA: https://docs.microsoft.com/en-us/azure/multi-factor-authentication/multi-factor-authentication-whats-next#remember-multi-factor-authentication-for-trusted-devices
Additionally, we’re looking at providing more controls for this through conditional access.Chad
supported this idea
·
-
91 votes
This is a scenario we are looking to support in the future however, it is not on our immediate roadmap for the next 6 months. Please continue voting and we will evaluate at a later date.
Chad
supported this idea
·
As per https://docs.microsoft.com/en-us/azure/api-management/api-management-policy-expressions#CLRTypes - you can use System.Net.WebUtility.UrlEncode with some notable differences - https://edi.wang/post/2018/11/25/netcore-webutility-urlencode-httputility-urlencode