I was tasked with setting up a Function environment. The Function was supposed to be hosted as a version 4 (~4) and was written in .net 6. No problem, right? Wrong!

## The error

This was the error I got:

Your app is pinned to an unsupported runtime version for '~4'. For better performance, we recommend using one of our supported versions instead: ~3.


To me that seems like a you problem but as ever Azure says it’s mine.

## The hunt

I used Bicep to deploy the Azure function, but in order to find all the settings that might be needed I opened the JSON view of the Function in the Azure Portal. The Function was pushed to development by the developer and it was up to me to deploy it in TEST and PROD.

The JSON view is an awesome feature. On the overview page of almost all services, you will find it up and to the right. It’s just a link:

If you click it, you get the JSON/ARM representation of the service:

You can find all the settings that you might want to look up, such as Always On or which server farm it is connected to.

## The find

I found this article from Microsoft, which I recommend, but at the same time it should not have to exists. It addresses all kinds of issues you can encounter when using Azure Functions 4.

## The solution

You need to tell Azure what version of dotnet you are using. This only needs to be done when using version 4 and .net 6.

properties: {
siteConfig: {
netFrameworkVersion: 'v6.0'
}
}


Then redeploy and the error message dissappears.

## The grief

Now the pitfall part is that if you look into the JSON view of the Function and try to find that setting … it is null. Even after your redeploy.

So, how are we supposed to know that needs to be set?

Boo! Boo I say.

# Bicep and static web apps

In my experience, static web apps is almost too easy. Setting up one is really easy and deploying code is only one single step! This too easy approach is found in setting up custom domains.

There is a really good and easy to follow article in the official docs. There is even a video showing you the process. It does not, however, show you how to do it using Bicep.

## My Bicep for provisioning the static app

Here is the Bicep I use to provision a new staticweb app:

var webappName = 'Identifier-${env}-stapp' resource staticwebApplication 'Microsoft.Web/staticSites@2021-03-01' = { name: webappName location: location properties:{ stagingEnvironmentPolicy:'Enabled' allowConfigFileUpdates: true } sku: { tier: 'Free' name: 'Free' } tags: resourceGroup().tags }  ## How to add a custom domain using Bicep The steps for adding a custom domain are outlined in the documentation linked above, but the steps are these: 1. Find your static web app’s autogenerated URL. 2. Update your DNS with a CNAME-record pointing your domain to that autogenerated URL. 3. Update the Custom Domain setting. (Run the Bicep update) Step 1 and 2 has to be done before running the Bicep update. ## The Bicep The official documentation is very limited I am sorry to say. That is the reason I wrote this post. Here is my Bicep for setting a custom domain: var domain = { PROD: { fqdn: 'smart.workdomain.com' } TEST: { fqdn: 'test-smart.workdomain.com' } DEV: { fqdn: 'dev-smart.workdomain.com' } } resource staticwebApplicationDomain 'Microsoft.Web/staticSites/customDomains@2022-03-01' = { name: domain[env].fqdn parent: staticwebApplication }  A couple of things to point out. • The parent is the static web app created above. • You do not need to add your SSL-cert, Azure takes care of that for you. Almost too simple. • The name is the domain you need to add. • Adding the domain takes about 10-15 minutes. So don’t give up. At work I always get new Azure Services to deploy and I always use Bicep. Here is how to manage network settings for PostgrSQL flexible server. This is the service one, not the “run on a Linux VM one”. ALWAYS use the service flavor. ## Basic PostgreSQL bicep Getting the Bicep from an existing Azure resource is super simple. Use VS code and the Command Palette (Ctrl+Shift P) and type Bicep: Insert Resource. Bom! There is your Bicep code and to understand it, here is the documentation reference. ## Network settings These are not found in the export and you have to add them manually (not great), but that is because it is a subtype. It is a separate type but can only exist when connected to another type. The definition is not hard to find: resource symbolicname 'Microsoft.DBforPostgreSQL/flexibleServers/firewallRules@2022-01-20-preview' = { name: 'string' parent: resourceSymbolicName properties: { endIpAddress: 'string' startIpAddress: 'string' } }  These are the same settings that you would use for an Azure SQL Server, it is just connected to a DBforPostgreSQL flexible server. Simply add all the IP-ranges you need to allow. Such as “the office in Stockholm” or “the consultant”. ### Allow Azure Services This is a special case and you need to configure a specific rule for it, allowing the IP-range 0.0.0.0 to 0.0.0.0. resource AllowAzureServices 'Microsoft.DBforPostgreSQL/flexibleServers/firewallRules@2022-01-20-preview' = { parent: PostgreSQLDB name: 'AllowAllAzureIps' properties: { endIpAddress: '0.0.0.0' startIpAddress: '0.0.0.0' } }  A while ago I posted an easy how-to guide for calling APIs in Dynamics 365 Finance and Operations (or D365 F&O to its friends). In that post I looked for statuses of batch jobs. This is the follow up post on how to get notified when a batch job is done. ## Batch job and alerting You can configure a batch to send you an e-mail when the batch is done, or errored, but an e-mail is not very computer to computer friendly. I needed a response back so the next action (or batch) could be executed. If you only need an e-mail when a batch is done. I suggest you check out this page. I am actually surprised that this is not a feature in D365 but it is easy enough to build using Logic Apps. ## The D365 APIs If you need information on connecting to the APIs you can find that in my last post Talking to the D365 F&O Rest APIs. The secret here is to use two features: A callback Url and a do-while loop. ### What is a callback URL? Glad you asked. When you call an API the operation might take a long time to complete, such as creating a new order or running a batch. Instead of either waiting for a very long time or getting a timeout, you give the call a callback URL. This URL is basically saying “When you are done, reply to this address”. When calling such an endpoint you supply the callback URL as a header or part of a message body, and the service should reply with a 202 Accepted, meaning “I received your message and will get back to you.” Setting up a callback URL is not the scope of this post. In my scenario it was handled by Azure Data Factory and was just a tickbox. ## The Logic App flow Your exact needs may differ, but we decided on getting a batch ID and the callBackURL as properties of the POST body. The flow started the batch using the standard Logic Apps connector. Then the Logic App simply queries the “Batch Status” in the D365 Data API until the batch is not executing anymore. When the batch is done, or there is an error of some sort, we respond back using the callback URL. Here is what the Get Batch Status from Data-API looks like: Details about the call can be found in the earlier post. ## A warning! This will not work on so called “scheduled batch jobs”. The reason is that if you trigger them, ie set to waiting, they will just continue to wait until the scheduling kicks in. In the Logic App above this will respond back as an error. If you need to be able to trigger the jobs imediatly, you need to remove the scheduling. But that is kind of the reason why you need to do this anyway. ## Tips for testing If you trigger the Logic App using Postman you cannot really handle the callback and you need to setup another endpoint for your Logic App to respond to. I used RequestBin, which solves this problem 100%. ## Conclusion Setting this up is really easy and I am sure you can do it using Power Automate. I am just a Logic App guys and likes solving things using Logic Apps. Adding this to your Azure Data Factory or similar makes you able to call a pipeline “when the first one is done” instead of using scheduling. # The F&O Rest APIs I decided to rewrite the article(s) from Microsoft about how to communicate with the Rest APIs in D365. The reason being that almost all documentation is written from the perspective of a person who knows a lot about D365 and how it works. If you are like me; you just want the data. I will walk you thru how to setup authentication, how to authenticate and where to find data. This is probably a bit lengthy, so feel free to use the ToC to read about the thing you need to know. ## Setting up authentication This is done in three parts: Create an application registration (identity), assign access rights, and register in D365. ### Create an application registration This is very similar to how you usually handle autheticating to Azure APIs. Setup an App Registration with a client secret. I made a Just make it work post on this. ### Assign Access Rights This is easier than you might think. In the left menu click API Permissions. Then find and click + Add a Permission. In the flyout menu to the right scroll down and find the Dynamics ERP option. Click on Delegated permissions and select all options. Yeah this seems like too much but according to the official documentation it is ok. ### Register in D365 This is straight forward. Just follow the official documentation: 1. In Finance and Operations apps, go to System administration > Setup > Azure Active Directory applications. 2. Select New. 3. Fill in the fields for the new record: • In the Client Id field, enter the application ID that you registered in Azure AD. • In the Name field, enter a name for the application. • In the User ID field, select an appropriate service account user ID. For this example, we have selected the Admin user. However, as a better practice, you should provision a dedicated service account that has the correct permissions for the operations that must be performed. 4. When you have finished, select Save. ## Authenticating In order to authenticate you need to get an OAUTH token, just like with any Microsoft API. However, there are some important differences. I will be using Postman to create and issue calls. ### Preparing Postman Your life will be much better if you use variables rather than hard coded values. Create the following: Global Variable name Value Comment G_AzureTenantId The Id of your Azure tenant Use the application registration overview page or visit https://www.whatismytenantid.com/. Environment Variable name Value Comment D365clientId Client ID The client Id of the application registration created earlier. D365clientSecret Client Secret The client secret of the application registration created earlier. D365InstanceUrl D365 URL The whole URL of the D365 instance you want to communicate with. Includes https at the start of the string. Example: https://myinstancename.testperhaps.dynamics.com Collection Variable name Value Comment c_bearertoken Empty Will contain the OAUTH token after authentication ### Setting the URL You need to create a new POST with this URL https://login.microsoftonline.com/{{G_AzureTenantId}}/oauth2/v2.0/token This is so Azure AD knows where to route the call, and you need to point it to your Azure tenant. ### Create the body • Select the “Form-Data” option. • Select Bulk Edit (to the right) • Paste the following into the window Client_Id:{{D365clientId}} Client_Secret:{{D365clientSecret}} grant_type:client_credentials scope:{{D365InstanceUrl}}/.default tenant_id:{{G_AzureTenantId}}  This will use the variables you created earlier. ### Create a Test This is not really a test but a way to get the returned access token into the collection variable c_bearertoken, for use in other calls. Add this code as a test: if (pm.response.code == 200) { pm.collectionVariables.set('c_bearertoken', pm.response.json().access_token) }  ### Test your call You are now ready to get a token. Click Send. You should receive a 200 OK and a response body like this: { "token_type": "Bearer", "expires_in": 3599, "ext_expires_in": 3599, "access_token": "ey ... KMw" }  If you want to, you can copy the access token and paste it into the windows at jwt.ms to get more information. The Roles array should contain the roles you assigned earlier. Please note that a token is only valid for one hour. After that you need to get a new one. Verify that the collection variable c_bearertoken has been populated. ## Calling and exploring the data APIs These APIs can get information about, and to some extent manipulate data in your D365 instance. In my case I want to get the status of a given batch. This scenario will be covered in depth in another post. To find in-depth information about the D365 data RestAPIs you can try to negotiate the official documentation. This is useful when you need to answer questions like “How to use enums in queries?” I will use the so called OData endpoint. ### Adding authorization to your call This will be a collection wide setting. Update your collection according to: Type: Bearer Token Token: {{c_bearertoken}} This will add your access token from earlier to all calls. ### Construct a call The basic enpoint is Your D365 Instance/data. In postman create a GET that uses this URL {{D365InstanceUrl}}/data. Make sure the Authorization option is set to Inherit from parent. Click send and receive a huuuuge list of all the data objects in your D365 instance. ### Exploring the API Where can I find batch jobs? I needed to get information about the status of a batch job. In the response body I searched for the word batchjob: This tells me that there is a data object called BatchJobs. Add it to the URL of the call: {{D365InstanceUrl}}/data/BatchJobs. VERY IMPORTANT!!! The data object name is case sensitive! {{D365InstanceUrl}}/data/batchjobs returns a 404. There is a list of all the batch jobs! The call to list the batch jobs took 15 seconds and the list is very long, but looking at each entity there is a Status field. This is what I need. Now, can I get the status of a single batch job? Using$filter?

According to the documentation you can use all kinds of sorting and filtering, which is very good but also something I expect from an OData API.

If I want to find information on Batch Job 5637515827 I can filter for BatchJobRecId using standard API filter syntax.

Update the URL to {{D365InstanceUrl}}/data/BatchJobs?\$filter=BatchJobRecId eq 5637515827. This will return an array with the specific ID.

## More exploration

Now that you know how to do the basic things, like authenticating and navigating the APIs, you should be able to get all kinds of information about the state of your D365 instance.