Microsoft Booking is an easy to use app for booking & scheduling introduced as Office 365 suite. Please refer below link for more about Microsoft booking

https://www.microsoft.com/en-us/microsoft-365/business/scheduling-and-booking-app

Please find the below steps to publish business calendar with Microsoft booking.

https://support.microsoft.com/en-us/office/publish-your-business-calendar-online-with-microsoft-bookings-47403d64-a067-4754-9ae9-00157244c27d?ui=en-us&rs=en-us&ad=us

This app can be Connected to Dynamics 365 or any other business apps. It makes possible to expose booking services to POS, call-center and with tight integration to our Dynamics 365 solution. Please find below API overview for integration.

https://docs.microsoft.com/en-us/graph/booking-concept-overview

Here is a link to publish it to Facebook seamlessly

https://support.microsoft.com/en-us/office/connect-microsoft-bookings-to-your-facebook-page-858db050-3d10-4bb5-82f1-df6ebeda2685?ui=en-us&rs=en-us&ad=us

Let’s welcome to a new member in Dynamics 365 family with features of mixed reality i.e. Microsoft Dynamics 365 Product Visualize which helps sales executive to showcase and customize products in a real-world environment.

This helps to create a shared understanding between buyer and seller to accelerate complex sales processes. In industries like manufacturing, healthcare, and automotive, where products are often complex and highly configurable, or simply too cumbersome to carry around, the need for product visualization is key. It builds a buyer’s confidence early in the sales process, so costly change orders are reduced, and customer satisfaction is higher.

Please refer below link for more information:

https://docs.microsoft.com/en-us/dynamics365/mixed-reality/product-visualize/

Preview Version can try using below link:

https://dynamics.microsoft.com/en-sg/mixed-reality/product-visualize/

Empower technicians to collaborate more efficiently by working together from different locations with Dynamics 365 Remote Assist on HoloLens, HoloLens 2, Android, or iOS devices. It can be a friend or accompany to Dynamics 365 Field Service.

Use Cases are as under:

Collaborative maintenance and repair

Remote inspections

Knowledge sharing and training

Please find the more details here —> https://docs.microsoft.com/en-us/dynamics365/mixed-reality/remote-assist/ra-overview

Want to try refer this link —>https://dynamics.microsoft.com/en-sg/mixed-reality/remote-assist/

UIFlows entered to the RPA market equipped with major RPA capabilities like attended, unattended,AI capability and many more..

Please refer below link for more details

https://flow.microsoft.com/en-us/blog/announcing-general-availability-of-robotic-process-automation-in-microsoft-power-automate/

Please refer below link for pricing information

https://flow.microsoft.com/en-us/ui-flows/

1. Dynamic 365 for Outlook will be deprecated.
2. Dynamics 365 Home will be deprecated.
3. Rules feature in canvas apps will be deprecated.
4. Legacy web client will be deprecated.
5. Task flows will be deprecated.
6. Some client APIs will be deprecated.

For details please refer :

https://docs.microsoft.com/en-us/powerapps/developer/model-driven-apps/client-scripting

7. Standard SLAs in Dynamics 365 Customer Service will be deprecated

For more details information please refer below link :

https://docs.microsoft.com/en-us/power-platform/important-changes-coming#dynamics-365-home-is-deprecated

We are mostly acquainted with What’s app but we rarely use the app released by Microsoft which is a secure chat platform.

Microsoft Kaizala is a mobile messaging (chat) app for large group communications and work management for modern workplace which enables organizations to communicate efficiently and securely with their Firstline Workforce, the value-chain outside the organization, and even their customers. It facilitates secure large group communication & discussion, message broadcast, work management, and complaint redressal, leading to better information flow and higher productivity. Please refer below link for more information.

https://www.microsoft.com/en-us/garage/wall-of-fame/microsoft-kaizala/

Please find the below links from Kaizala setup to integration with Dynamics 365

Microsoft Kaizala -Initial setup with trial version

Kaizala -Initial configuration

Kaizala – How to integrate with business applications?

Kaizala – How to integrate with business applications?- Part 2

Kaizala – How to integrate with business applications – Dynamics CRM – Part-3

Developers often get confused what the difference is between the three different menu item types shown in AOT and when should you use them as it appears that all menu items inside the three ‘folders’ I would say have the same set of properties and support the same object types. So, what is the difference? The answer is that there is no difference, the difference is a conceptual one rather than a functional or a technical one.

1. Display Menu item

This folder is used to contain menu items that reference runnable objects which are primarily for presenting data to the user such as forms and dialogs.

2. Output Menu item

An output menu item should have the sole purpose to print a result, mostly used for referencing classes.

3. Action Menu item

As the name says it, you should create a menu item under this folder if your runnable object has an action to perform, for example creating or updating data.

So, choosing between these three is on the developer’s sole discretion and I hope now you’ll be able to make a better choice for your scenario. A basic rule of thumb is:

• Display – This type is used for opening forms in the web browser
• Action – This type is used to start periodic tasks or update processes
• Output – This type is used to start reports

Elements:

• Dynamics 365 for Finance and Operations represent every individual element of AOT such as class, table, form, and so on.
• Elements in Dynamics 365 for Finance and Operations are stored on disk as XML files; these files contain the metadata and source code for the element.
• The XML files are the unit of Source Control

Projects:

• works the same as AX2012, but in D365 an element can be customized only once they are added to a specific Visual Studio project.
• The project may only belong to one model.

Dynamics 365 for Finance and Operations model:

• This is a group of elements. Standard elements are part of a standard model; you can add them into your model and do customization.
• A model is a design-time concept. An example of models: warehouse management model, a project accounting model, and more.
• Models can have one or more projects. Models may only belong to one package.

Dynamics 365 for Finance and Operations package:

• This is a deployment and compilation unit of one or more models. It includes model metadata, binaries, cubes, and other associated resources.
• One or more D365 packages can be packaged into a deployment package, which is the vehicle used for deployment on UAT and production environments.
• Packages are packaged into a deployable package file for deployment to Sandbox or production environments.
• A package can have one or more models. Packages can have references to other packages, just like .NET assemblies can reference each other.

How to create a Project in Visual Studio:

How to create a Model in Visual Studio:

There was one more step while creating a model, Select referenced packages.

When you create your own package, you can select from an existing package to add them as references in your new package. You may need to add some standard package reference if you want to add them into your customization

Microsoft power platform API request allocation is based on type of licensing.. normally this question comes during presales stage to know the capability of the product and its limitations which includes costing obviously 🙂

Please click on below image to know more about request limits…

Please find the below licensing guide for power platform for detailed information :

https://download.microsoft.com/download/9/5/6/9568EFD0-403D-4AE4-95F0-7FACA2CCB2E4/Power%20Apps%20Power%20Automate%20and%20Power%20Virtual%20Agents%20Licensing%20Guide%20-%20Feb%202020.pdf