I’m interested in hearing more about your C++ scenarios. If you have a few minutes to chat, please shoot me an email at email@example.com.
- Matt McCleary, Product PM
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
Of course this is not stopping anybody from using asp .net core 2.2 on nano server.
I used version 2016 and it runs asp.net core 2.2 too.
The tags page with 2016(1607) images is
The tag I used as runtime is
and the tag I used for build is
Additionally you can find here https://docs.microsoft.com/en-us/azure/app-service/app-service-managed-service-identity
a note saying the same thing regarding Azure Functions with managed identity in AD (If I am not totally wrong) :
Managed identities for App Service and Azure Functions will not behave as expected if your app is migrated across subscriptions/tenants. The app will need to obtain a new identity, which can be done by disabling and re-enabling the feature. See Removing an identity below. Downstream resources will also need to have access policies updated to use the new identity.
Thank you for your feedback. We are currently working on providing this functionality and will provide updates when they become available. See the following article for the latest: https://docs.microsoft.com/en-us/rest/api/storageservices/status-and-error-codes2. Note that for REST API version 2017-07-29 and later, failed API operations also return the storage error code string in a response header. For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.
Yeah! When I see : 'The remote server returned an error: (500) Internal Server Error.'
I do not get excited about debugging it.
Come On! Do it! You can do it! :)
: 'The remote server returned an error: (500) Internal Server Error.'
You can see that these two stackoverflow posts are viewed more then 50k times :
And these two are just the first I stumbled upon.
Thank you for your feedback. We are currently in public preview of blob storage lifecycle management. The feature set offers a rich, rule-based policy engine which you can use to transition your data to the best access tier and to expire data at the end of its lifecycle. See our post on the Azure Blog to get started: https://azure.microsoft.com/en-us/blog/azure-blob-storage-lifecycle-management-public-preview/preview/.
For any further questions, or to discuss your specific scenario, send us an email at DLMFeedback@microsoft.com.
Our apologies for not updating this ask earlier. Renaming Blobs is on our backlog, but is unlikely to be released in the coming year. Today, you can use the “Copy Blob” API as a workaround.
Using the Azure Files service you can address Azure Storage like a network share using the SMB2.1 protocol. This enables usage of normal Windows API’s to rename files and directories. You can get started with the Files service by visiting https://docs.microsoft.com/en-us/azure/storage/storage-dotnet-how-to-use-files.
For any further questions, or to discuss your specific scenario, send us an email at email@example.com.
This is something we’re still actively working on. It has a been a big area of investment and it still is moving forward. We keep investing in performance, both from a client and server side perspective.
We have a few things coming in the near future which should help address some of the initial UI performance issues. We’re also heavily engaged with all of our partners driving a broad effort to improve performance across the portal for all experiences.
If you have any specific areas which are causing pain please feel free to reach out to me or comment and state if we can contact you, it would be great to understand the common pain points.
I suppose that placing a node of the web instance or just a caching node in every country will do the job just fine.
AAD currently requires a strict directory scoping. We can investigate options if this is a popular request.
@Gelande Strasse are you looking for this - https://snag.gy/faJlsV.jpg
Looks like it is implemented
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
Thank you for your feedback. We will consider ways to implement this.
We have done a lot of progress on this area in last few years, and we would like to know if there is something scenario specific that you guys are looking for?
Azure Portal Team