Business events in Dynamics 365 Finance & Operations and Microsoft Azure Service Bus

1. Create a new Service Bus namespace.

2. Create a new Service Bus Queue.

3. Create a new key vault to store the Service Bus key.

4. Register an Azure app that has permission to access the key vault.

5. Configure a Business Events endpoint.

6. Consume the business event.

1. Go to the Azure portal.

2. Select All services > Integration > Service Bus.

3. Select Add to create a new Service Bus namespace and set the parameters. Select the Standard pricing tier. You can create a new resource group as a container for your lab, or you can use an existing resource group.

1. In the Azure portal, select the Service Bus that you just created, and then create a new queue.

2. Go back to the blade for your Service Bus and create/configure a new shared access policy to send events. Only the Send policy is required to send events to the Service Bus queue.

3. Select the new Send policy, and then copy and save the Primary Connection String value. You will use this value later.

1. In the Azure portal, select All services > Security > Key vaults.

2. Create a new key vault in your resource group and set the default parameters. Click review + create. Wait till resource is deployed.

3. Select Overview, then copy and save the Vault URI value for the key vault. You will use this value later.

4. Select BETestServiceBusKeyVault > Secrets > Generate/Import. Enter a name for your secret and paste the Service Bus connection string that you saved earlier.

5. Select Create.

1. In the Azure portal, select All services > Security > Azure Active Directory.

2. Select App registrations (preview) > New registration, and enter a name for your application. Select Register.

3. Select the new application, and then select Certificates & secrets > New client secret. Enter a name for your secret and set the secret so that it never expires. Then select Add.

4. Copy and save your new secret. You will use it later.

5. Select Overview, and copy and save the application ID. You will use this value later.

6. Select All services > Security > Key vaults.

7. Select the key vault that you created earlier, and then select Access policies > Add new.

8. On the Principal blade, select your new registered application. Select the check all boxes for the Key management operations, Secret management operations and Certificate permissions.

9. Save your new access policy.

1. Sign in to the application and go to System administration > Setup > Business events.

2. Select Endpoints.

3. Select New.

4. Select Azure Service Bus Queue.

5. Select Next.

6. Set the required parameter values.

1. Select the business event catalog and look for Invoice journal business event.

2. Activate the business event for USMF company.

3. To verify that the test message has been received, in the Azure portal, select your created queue, and check for a message in it. Verify that the message count for the queue shows a value of at least 1. If it doesn’t, wait for the batch job to pick up your message.

4. Select All services > Integration > Logic Apps.

5. Create a new logic app in your resource group.

6. After your Logic Apps resource has been created, select the option to create a blank logic app.

7. Search for Service Bus and select it.

8. Select the trigger that is named When a message is received in a queue (auto complete).

9. Select New step to add a new action.

10. Search for the Parse Json data operation. This step is required so that the message can be parsed by using the schema of the data contract.

The body content that is received from the Service Bus is encoded into base64 format. Therefore, you must transform it to string format before the JavaScript Object Notation (JSON) payload can be parsed.

11. Click in the Content field, and then, in the pane that appears, on the Expression tab, enter the following expression: Base64ToString()

12. Select your event in the business event catalog, and then select the Download schema link. Open the text file that is downloaded and copy the contents.

13. Depending on the quality of your sample payload, your generator won’t be able to distinguish between an integer and a real value, especially if the real value is provided as a whole number in the sample payload. Review the schema that is generated and determine whether you must change a field of the integer data type to the number data type. (In JSON, the number data type represents real values.)

14. Search for the send email action, and then sign in to your Microsoft 365 account.

15. Fill in the message with the required fields.

16. Save your logic app.

17. Trigger the business event by calling send method from code. Then verify that the logic app runs, and that you receive an email that includes customer payment details.