Quick update here that we’re still planning to do this. It will take us some time to complete, but we’ve heard your feedback and know how important it is.
In the meantime we would love to hear more about the type of data points you would like to see.
We are currently developing a solution to allow you to assign a region to applications outside the region of your home tenant. By doing this, connector groups will talk to the App Proxy region specified. Please continue to share your scenarios to make sure we are taking into account these cases.
We will update once we have a better idea for a release date.
Send a note to firstname.lastname@example.org if you have questions or want to send feedback directly to us.
We are looking at enabling a feature that focuses on supporting CORS preflight requests between two applications. This works by allowing you to configure the response and have App Proxy handle it on behalf of the app.
A pre-requisite for this feature to work is that the user must be able to authenticate into the second application in order to avoid a CORS issue from the login flow into the second app.
To avoid this the user will have to make sure they have already accessed the 2nd application before the CORS request, and has valid credentials. This should work for wildcard apps and can also be achieved by adding a fake link / image to the 2nd application in the first application.
We would love to get your feedback on this requirement and if this is something that will fit your use case.
19 votesplanned · 5 comments · Azure Active Directory » Azure AD Connect · Flag idea as inappropriate… · Admin →
We are currently investigating how to implement this. The expiration status is not a directory attribute so it is not straight forward how to sync it.
48 votes14 comments · Azure Active Directory » Provisioning to Applications · Flag idea as inappropriate… · Admin →
The first issue is fixed as described here: https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/application-provisioning-config-problem-scim-compatibility
OAuth authorization code grant flow is now supported for new apps that want to be added to the Azure AD app gallery. You can request your app be added here – https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-app-gallery-listing
Work to support the code grant as well as client credentials on the non-gallery app is currently in our backlog. It’s intended to be done, but not yet funded.
In the meantime, the 1KB token limitation has been lifted.
An error occurred while saving the commentArindam Laha commented
Is there any update on this topic? Azure AD SCIM is not implemented as per the RFC guidelines.
4 votes2 comments · Azure Active Directory Application Requests » User Provisioning · Flag idea as inappropriate… · Admin →
Please try the steps outlined here and confirm if they work.https://docs.microsoft.com/azure/active-directory/saas-apps/oracle-cloud-infratstructure-console-provisioning-tutorialArindam Laha shared this idea ·
3 votes0 comments · Azure Active Directory Application Requests » Single Sign-On · Flag idea as inappropriate… · Admin →
14 votes0 comments · Azure Monitor-Log Analytics » Active Directory Assessment Solution · Flag idea as inappropriate… · Admin →
This seems a very specific requirement, let’s see how many need this…
Maybe this type of scenario is more appropriate for the ‘Security and Audit’ intelligence pack http://feedback.azure.com/forums/267889-azure-operational-insights/suggestions/6519064-security-event-logs-should-be-collected which allows more ad-hoc exploration on the data that Windows already logs (if you enable certain audit policies).
AD Assessment performs specific configuration checks that can ‘pass’ or ‘fail’ – a list of groups is not a possible output for that model.