We also need this functionality. We would like to move our files storage off of Sharepoint, but we need to be the same audit capabilities as O365.
172 votes3 comments · Azure Kubernetes Service (AKS) » Support for Kubernetes features · Flag idea as inappropriate… · Admin →
186 votesstarted · 20 comments · Azure Kubernetes Service (AKS) » Integration with Azure services · Flag idea as inappropriate… · Admin →
We are waiting on more feedback around this.
This feature is currently in active development. We will update this item to complete once it has shipped so those voting/commenting will be notified.
Thank you for your patience.
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.
The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.
Once that is released we will mark this feature as complete.
Thank you for your patience and votes.
We will work towards moving our platform to Cosmos once this feature is added.
We continue evaluating several alternatives to provide full email customization. We are actively working on an alternative.
Unfortunately we do no yet have an ETA.
Please add functionality that allows for email sending from customer domains. I know this is tricky and would likely require domain owners to add SPF records to their DNS, but it something that is preventing us from using B2C for some our client initiatives.
It is also important that these email can be sent from the customers domain, rather than from email@example.com. There is a separate backlog item started to support B2C on Customer Domains. Perhaps this efforts can be combined?
Due to various technical limitations, the first iteration of the customer-owned domains functionality will not be available for a few more months. We will provide an update as soon as we can get a more specific ETA.
We’ve put out a new version of the sign in policy called sign in v2. This is available through the new portal experience and we have rebranded policies as user flows. Please give this a try and give us feedback through this link: https://microsoft.qualtrics.com/jfe/form/SV_0Gu45RkBy2YR1kh
We have a sample for this use case here: https://github.com/azure-ad-b2c/samples/tree/master/policies/invite
Let us know what you think and if this fits your use case.
We recently announce the General Availability of Azure Active Directory Domain Services (Azure AD DS) authentication for Azure Files! By enabling integration with Azure AD DS, you can mount your Azure file share over SMB using Azure AD credentials from Azure AD DS domain joined Windows VMs with NTFS ACLs enforced. For more details, please refer to our blog post:http://aka.ms/azure-file-aadds-authentication-ga-blog.
A part of the GA announcement, we shared the upcoming plan to extend the authentication support to Active Directory (AD) either hosted on-premises or in cloud. If you need an Azure Files solution with AD authentication today, you can consider installing Azure File Sync (AFS) on your Windows File Servers where AD integration is fully supported.
If you are interested to hear future updates on Azure Files Active Directory Authentication, please complete this sign-up survey:https://aka.ms/AzureFilesADAuthPreviewSurvey.
Azure Files Team
This is something our organization needs. I hope is a feature that gets added soon!
We need this feature to ensure that when an employee leaves, they no longer have access to storage accounts.
We have released the public preview for this feature! Learn more about how to use it here: https://docs.microsoft.com/azure/active-directory-b2c/active-directory-b2c-setup-oidc-azure-active-directory
Adding the ability to integration AAD providers is critical for our organization. How do we get involved in testing this functionality?
We use a storage account per customer application. We got our limit increased to 250, but we will soon run out. We don't need a huge amount of space per storage account, so perhaps azure should limit on space used and not storage account. Also, we create a resource group per customer application. When a project ends, we can delete that resource Group, and all of its resources are removed (including the individual storage accounts).
Thank you. We will examine the experience of duplicate sign ups across Identity providers. Would performing this check by using the email address be sufficient?
BTW, Linking multiple provider accounts to one user is in our roadmap and we’ve already achieved it in preview…
We look forward to your feedback
317 votesunplanned · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
This is not currently planned at this time. Will keep this item open for voting and comments.