We had an external code review and security check done for our product. One of the items highlighted was Azure B2C's use of old version of JQuery (version used by B2C is 1.10.2). We were wondering if there is a plan by Microsoft to update the JQuery version used by B2C?
Yes we plan to ship page contracts soon (vote on the link below for updates) that allows us to change the versions more easily without breaking existing production environments. We will then make the updates as needed.
https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/15493536-add-support-for-javascript-inside-the-custom-ui-br
Related
I am thinking about using Pulumi for Azure and was curious how up to date the API support is. I checked the storage account as an example.
Pulumi: API Version 2021-02-01
latest version according to Microsoft docs: API version 2022-09-01
Isn't that an issue? How fast is Pulumi in adding features from new API versions?
Pulumi automatically generates new SDK versions that are always up to date with the Azure APIs. So even though the documentation you linked might not show the newest version, the SDK already supports it.
https://www.pulumi.com/blog/full-coverage-of-azure-resources-with-azure-native/
Unlike the classic Azure provider, which requires manual work to keep updated, we designed the native provider to stay always up-to-date with Azure API additions and changes. We generate Pulumi SDKs for the native Azure provider automatically from Azure API specifications published by Microsoft. We publish daily builds of the provider and have published 210 versions of the provider in the last six months.
You can find the sources for the API version you mentioned on GitHub: https://github.com/pulumi/pulumi-azure-native/tree/master/sdk/dotnet/Storage/V20220901
When creating an Azure Static Site using the Blazor settings, you get an option to configure an API. My repository has an Azure Functions V3 API, and I want to use that. After making all the definitions, the build and deploy workflow fails. When I eliminate the api_location setting, the workflow succeeds.
I am pretty sure that the workflow expects a V2 Azure Functions application.
Can I supply a custom build command to build the V3 application?
Will role management work OK with V3?
Thanks!
According to this, a managed API can only use .NET Core 3.1, while V3 is .Net 5 based, so that is probably why the build failed.
Having said that, this document is from May 2020, so this maybe changing soon, hopefully...
Update: After discussing the matter with a Microsoft employee involved with the matter, they informed me that (a) the document is indeed up to date and (b) static apps API will .NET 6 support sometime in November...
I'm developing Azure DevOps extension. When client download extension he can register in Azure Hub then his account is added to my database.
When the client delete extension his account should also be removed from my database.
How can I add process for Azure DevOps extension that can be triggered on uninstall / remove extension?
I don't think there is an API for this, but you can see uninstalls here in the Marketplace portal. I guess you could poll this, or figure out the underlying API that's being used. any integration against these APIs is unsupported.
https://marketplace.visualstudio.com/manage/publishers/{PublisherID}/extensions/{ExtensionID}/hub?_a=uninstall
Also, remember that for troubleshooting purposes people uninstall/reinstall extensions and they may need to reinstall as part of migration/upgrade scenarios for which their assumption is likely going to be that no data is lost in the progress.
It's probably best to ask for contact details, upon registration, monitor usage and warn that data will be removed after X days of no usage.
When visiting the url - https://developer.microsoft.com/en-us/graph/graph-explorer
In the graph explorer it has a drop down 1.0 or beta. Is beta version 2.0 that Microsoft references in all of it's documentation?
https://learn.microsoft.com/en-us/azure/active-directory/develop/azure-ad-endpoint-comparison
This would be a great question answered because I do not see a drop down for v2.0
There are a couple of things to differentiate here. Azure active directory is the central identity service behind most of Microsoft SaaS services.
It provides two main things
a central identity database that stores users, groups and more. It can be accessed via the graph.windows.net API. Although it's recommended to use the Microsoft graph instead now.
authentication and authorization services. That live mostly under login.microsoftonline.com.
The later provides two versions of the service v1/v2 that implement different capabilities and protocols. (Second documentation link you're providing).
The Microsoft graph on the other hand is the central API for Microsoft 365 services.
The v1 is supported for production workloads, Microsoft is not going to break the API contract and keep the services behind it up and running.
The beta endpoint is where Microsoft makes new things available to get some feedback. Not meant for production workloads. When those new capabilities are ready for prime time, they'll show up under v1.
There's no v2 as of today for the graph. They'll publish a v2 once they need to publish breaking changes to existing capabilities to avoid breaking v1 and disrupting customers.
As a Microsoft Azure services client, I received earlier today the following mail: http://aka.ms/Qga48e.
I was wondering how I could migrate my Blob storage without services disruption to use the latest Azure File Storage service.
Anybody has already performed this action? Any feedbacks will be welcomed.
Thanks.
I don't think that it would be necessary. Besides Azure Blob Service and Azure File Service serve different purposes all together and the things you could do with blob service can't be done through file service.
As mentioned in the newsletter, what you should try to do is upgrade your client applications to make use of latest version of storage client library. If you're using an older version of library (< 2.0), there would be some pain in migration but migrating from 2.0 to 4.x (currently latest version) should be rather painless.
Next thing you should look into is the default service version of your storage account services. If you're using .Net storage client library, you can fetch it via GetServicePropertiesAsync method. You can update the default service version using SetServicePropertiesAsync method.
You may also find this link helpful about understanding storage service versioning: http://msdn.microsoft.com/en-us/library/azure/dd894041.aspx.
UPDATE: 13-DEC-2014
Azure Storage Team has published a blog post which talks more about this issue: http://blogs.msdn.com/b/windowsazurestorage/archive/2014/08/05/microsoft-azure-storage-service-version-removal.aspx.
The Storage Service REST API is not being removed. There are several versions of the API, from over the years. Older versions of the REST API (prior to the 2012-02-12 version) are being retired. But it's definitely not going away, and neither is the Azure Storage service.
Different versions of the SDKs (across the various language stacks) and command-line tools (PowerShell, CLI) may be using one of the older versions. If you're using the current versions of SDKs and command-line tools, this has no effect on you.
Consider how many versions there have been (all tracked here, and all listed in the page you linked to in your answer:
2014-02-14 (current)
2013-08-15
2012-02-12
2011-08-18
2009-09-19
2009-07-17
2009-04-14
If you're using an older version of an SDK or command-line tool, there's a chance that, in Dec. 2015, it won't work as expected anymore, as the underlying version will have been retired. So, essentially you have until December 2015 to update your Azure projects if needed.