102 votesstarted · 7 comments · Networking » Azure Front Door Service · Flag idea as inappropriate… · Admin →
I have deleted my previous comment and removed my 3 votes because, as it turns out, there is a perfectly acceptable way of dealing with this issue. For people having the same problems here are the basics:
Application Insights allows you to mark requests from certain user agents as synthetic. In the full framework version of the SDK this is done in the ApplicationInsights.config file (look for SyntheticUserAgentTelemetryInitializer, or for more information about this file: https://docs.microsoft.com/en-us/azure/azure-monitor/app/configuration-with-applicationinsights-config). In the .NET Core version of the framework you might need to write a simple custom TelemetryInitializer yourself that inspects the request's user agent and marks the telemetry accordingly.
When everything that is synthetic is marked as such, you can add a simple custom ITelemetryProcessor implementation to filter out all synthetic requests. For an example, see: https://docs.microsoft.com/en-us/azure/azure-monitor/app/api-filtering-sampling
We are planning to do this in the next 6 months, however it will only be possible through the Graph API.
Any news on this? Those 6 months are over by now, and I am getting customer questions regarding this feature.
We are looking to add additional MFA options for Azure AD B2C in the next few months. As part of the investigation, we want to learn more about your requirements. Email your feedback to firstname.lastname@example.org.
When you say “support for Microsoft Authenticator”, which feature are you referring to?
1. The ability to see the codes in the authenticator app
2. The ability to receive push notifications for MFA
If both, which do you prefer more?
Again, please email your feedback to email@example.com. Feel free to include more details about your scenarios/requirements!
We have a private preview of this feature available. If you are interested in joining, please contact firstname.lastname@example.org with the name of your tenant.
At least allow us to be able to conform to most NIST standards as described in the following articles (and ofcourse the NIST website):
This is planned. Thought there was another issue to merge with but couldn’t find it – so keeping this for now.
We understand this is a top customer ask and as such it is currently on our backlog to be prioritized. We will update when the status changes.
This would work even better if we could easily query for a list of partitions in the table.
The most simple solution I would see that would work for us, is where we could specify the table name for the output from a column in the input event, or for instance as a constructed string. So for instance this kind of syntax:
CREATE TABLE input_source (
SELECT DeviceId as PartitionKey, Moment as RowKey, Value
INTO 'Organization' + OrganizationIdVossekop shared this idea ·