For Windows apps you can check the 'WEBSITE_NODE_DEFAULT_VERSION' in Configuration > Application settings. For Linux Apps, you will need to run az functionapp config appsettings list --name <name> --resource-group <group> to get the info, but you can do that from the cloudshell in the portal if you do not want to run it locally.

For more details on Node runtime versions, you can check this doc: https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-node?tabs=v2#node-version

Regardless of the type of sampling involved or what the sampling rate is, App Insights will always do it's best to keep correlated events so that any data that is kept will also maintain the end-to-end transactions. If you are keeping 100% of the message logs, it should keep 100% of the correlated Receive messages, and will keep fewer of the heartbeat events. This principle should be applied even if it means keeping a higher percentage than what you have set for the request items.

This error is usually because of non-matching dependency versions, including upstream dependencies from the ones explicitly included. I was able to build with this dependency list with Azure version 3.2.0 in addition to Spring version Hoxton.SR8. Are there any other dependencies or projects involved that could be causing the conflict?

Can you explain a bit more what you are trying to do? Are you trying to use service principals for your function to connect to another service, to allow other services to access the function via a principal, or trying to manage principals with the function?

What are your plans for the data? Are you trying to query it regularly to find data, archive it without needing regular access, do additional processing, etc.?

SangilimuruganS,

It looks like you are working through this tutorial? https://docs.microsoft.com/en-us/azure/synapse-analytics/sql/create-external-table-as-select

Without sharing anything that would be sensitive info, can you give a little more detail on how MyDataSource23 is setup? The shared access signature given in the tutorial will not work on your storage account. Instead you would want to generate a SAS token for your storage account or use something like:

 CREATE DATABASE SCOPED CREDENTIAL [ManagedIdentity]
 WITH IDENTITY = 'Managed Identity';

And use that to setup your external data source.

You can use either SAS token or Managed Identity/Contributor role but not both at the same time. Adding the role doesn't help if you are using SAS.

The next thing to do is to make sure you are generating your SAS token correctly. They need to be generated for the specific container and they can expire:

Would you mind sharing the relevant portion of the app you are working with? I think I understand what you are trying to do overall, but I'm unsure of specifically what actions you are doing so I can replicate the scenario

Could you please share a link to the tutorial you are following?

Hi!

Are you feeding the data into the if/then filter as a string or as a json object? If you aren't sure, you can share the JSON definition (with proprietary info removed) and I can review from that.

Are you using the RM module or are you using the newer Azure Powershell modules in compatibility mode? I got different results with each and want to be sure I'm replicating this properly.

Hi @kdeman-8994 Could you share the guide you are following so I can understand how your B2C configuration is setup? Also, for the function app, are you setting the authentication up on the App Service Account/in the portal, or are you trying to authenticate users within the function code?

Just trying to make sure I understand the scenario correctly since you only posted one config file. Are you trying to deploy from three different repos a->a, b->b, c -> c, or are you using a single repo and trying to deploy to three different apps at different times?

The config server takes precedence if it is available. the application.yml works as a backup if the server is not available for some reason: https://stackoverflow.com/a/35545152/11002318