Wednesday 31 January 2024

{New} Use AI Builder to create GPT prompts

Hello Everyone,




Today I am going to share my thoughts on preview feature Prompt Builder to create GPT prompts.








Let's get's started.





The Prompt Builder for creating GPT (Generative Pre-trained Transformer) prompts is a specialized tool designed to assist users in crafting effective and precise prompts for AI models like ChatGPT.



This builder guides users through a structured process, helping them formulate queries that are clear, concise, and targeted  to elicit the most relevant and accurate responses from the AI.





It typically includes features like templates for common types of queries, suggestions for refining prompts based on the desired outcome, and examples of well-constructed prompts for various scenarios.






Additionally, the prompts, advising on adjustments to improve clarity or specificity.




This tool is particularly useful for those unfamiliar with how to interact with AI models or for complex queries where the precision of language is crucial.



By streamlining the prompt creation process, the prompt Builder enhances the user experience and maximizes the efficiency and usefulness of interactions with GPT-based AI systems.





That's it for today.


I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days

Tuesday 30 January 2024

Extend Copilot using AI Plugins to perform specific actions

Hello Everyone,







Today I am going to share my thoughts on Extending Copilot using AI Plugin to perform specific actions.








Let's get's started.



Extending a Copilot system with AI plugins to perform specific actions involves integrating specialized AI models or functionalities that enhance its core capabilities.





These Plugins can be tailored to execute distinct tasks, such as language translation, sentiment analysis, image recognition, or even domain-specific actions like financial forecasting or medical diagnostics.





By incorporating these plugins, the Copilot becomes more versatile, capable of handling a broader range of queries and providing more sophisticated responses.









The process typically requires identifying the additional functionalities needed, selecting appropriate AI models or services that fulfill these requirements, and integrating them into the Copilot 's existing framework.





This integration must ensure seamless interaction between the core AI and the plugins, maintaining consistency in user experience.





Additionally it's crucial to regularly update and fine-tune these plugins to adapt to evolving data patterns and user needs. This approach significantly enhances the utiltiy and adaptability of the Copilot. making it a more powerful tool in various scenarios and applications.






Note: To start using AI Plugin discovery and authoring, you can access all of your plugins from a central repository.








That's it for today.



I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days









































































Monday 29 January 2024

What is the significance of sending proactive messages in Microsoft Teams

Hello Everyone,





Today I am going to share my thoughts on sending the significance of sending proactive messages in Microsoft Teams.








Let's get's started.




Sending proactive messages in Microsoft Teams involves automating communications to initiate interactions without a user's immediate prompt, enhancing engagement and efficiency.




To do this, you can use Microsoft Power Automate or a custom bot developed with the Microsoft Bot Framework. 







With Power Automate, you can set up flows triggered by specific events or conditions, sending automated messages to Teams channels or users.





For a more advanced approach, a custom bot can use the Bot Framework to send messages based on complex logic or interactions. 





This feature is particularly useful for notifications, reminders or updates ensuring that important information is communicated promptly and automatically. 




However, it's crucial to balance the frequency and content of proactive messages to avoid over whelming users, and to adhere to Team's policies and best practises for bot interactions.








That's it for today.

I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days

Sunday 28 January 2024

What are the benefits of making your Copilot multilingual

Hello Everyone,





Today I am going to share my views on the benefits of making Copilot multilingual.








Let's get's started.





What are the benefits of the new feature of making Copilot multilingual?





So deploying multilingual Copilot, Users can be more effectively scale your localization efforts when building copilots and when providing support through your copilots.










Copilot users have control over the language they want to use when talking to your copilot, and you'll spend less time triaging and investigating escalating or failed chat conversations that are in multiple languages and across multiple locales.




Once this feature is enabled, Copilot users can also switch between languages during their conversations with the copilot.


Your Copilot have control over how they interact with Copilot and also getting correct information every time.




That's it for today.


I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days





Saturday 27 January 2024

{How to} Create Cloud Flows Just Describe it to design it from Power Automate

Hello Everyone,




Today I am going to show how to create a Cloud Flows Just 'Describe it to design it' from Power Automate.










Let's get's started.




Up until now you can create flows from Templates, Viso template, OR Build your own from blank

Automated cloud flows, Instant cloud flow, Scheduled cloud flow, Desktop flow.



New " Describe it to design it"










Now click on the Describe it to design it.











Then a new window will be displayed where you can describe what you want to auomate and AI will help you make it happen.




Ask Copilot " Send me an email reminder every week",










Then the suggested Flow will appear on the screen( see above), and click NEXT.









Office 365 users and Office 365 Outlook connections established and click on Create Flow.













Here you go, Cloud Flow created with few simple steps with natural language description.




That's it for today.



I hope this helps.


Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days





























Friday 26 January 2024

{How to} Check Power Automate License from Power Automate Settings

Hello Everyone,






Today I am going to show how to check the  Power Automate License from Power Automat Settings.








Let's get's started.




Suppose you want to check your Power Automate Licenses as using some connectors requires Premium License.










1. Login into Power Automate.



2. Click on Settings





3. Click on the View My Licenses.








As you can see from above screenshot:

My licenses defines are authorised power automate licenses including the Microsoft Service Copilot Viral Trail.



That's it for today.


I hope this helps,

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days

Thursday 25 January 2024

{How to} Turn on Experimental Features on Power Automate from Power Automate Settings

Hello Everyone,





Today I am going to show how to turn on experimental features on Power Automate FROM Power Autmate Settings.









Let's get's started.

        


1. Login into Power Automate.








2. Click on Gear Icon







3. Experimental Features Turned ON now.





That's it for today.



I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days



















Wednesday 24 January 2024

{Do you know} Create Power Automate Cloud Flows using Copilot

Hello Everyone,







Today I am going to share my thoughts on New Feature " Create Cloud Flows using Copilot for Power Automate".







Let's get's started.



Up until now,  we are creating Cloud Flows using drag and drop or clicks,  Now with the new feature user can give statement to the Copilot to create Cloud Flows.











Copilot in Power Automate allows open-ended and conversational experiences while authoring your flows.




While you are building flows you can ask question on Copilot and you will get assistance making improvements.







You dont need  knowledge of how power automate works.




Just type in normal speaking language and you will be able to build and enhance everything from a simple to complex flows.





That's it for today.



I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days























Tuesday 23 January 2024

{Do you know} Now you can connect to other environments from the Microsoft Dataverse connector

Hello Everyone,







Today I am going to share my thoughts on new features of Power Automate connect to other environments.









Let's get's started.




The infographic above illustrates the process of connecting to other environments using the Microsoft Dataverse connector, visually representing the integration and data exchange between different systems.








Up until now you can only use the Microsoft Dataverse (legacy) connector to connect to environments outside of the current environment.



So with this new feature, we can connect to other environments from the Microsoft Dataverse connector's actions and triggers.




That's it for today.

I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days

Monday 22 January 2024

{Do you know} Now you can use versioning for solution cloud flows

Hello Everyone,







Today I am going to share new feature benefits of using versioning for solution cloud flows.







Let's get's started.



Up until now you don't have versioning for solution cloud flows, there is a lack of ability to revert to a previous version.


With this new feature: you can view and restore past versions of solution cloud flows, This can save your time in recreating flows when you get errors which can't be resolve.



This ensures that business always has a working version.



Using Versioning for solution cloud flows in platforms like Microsoft Power Automate offers several key benefits that enhance the development, maintenance, and overall management of these flows.






Here are the main advantages:












1. Improved Change Tracking: Versioning allows you to keep a record of changes made overtime. This makes it easier to track who made changes, what changes were made, and when they were implemented, facilitating better change management.





2. Easier Rollback: If a new version of a flow causes issues, versioning enables you to quickly revert to a previous version that was stable and functioning correctly, thus minimizing downtime and disruption.





3. Enhanced Collaboration: In environments where multiple develpers or teams are working on the same flow, versioning helps coordinate changes and prevents conflicts. It allows for better collaboration and communication among team members.




4. Simplified Testing and Debugging:  Versioning allows for the testing of specific versions of a flow.

You can identify which version introduced a bug or an issue, making it easier to debug and fix problems.





5. Audit and Compliance: For regulatory compliance and audit purposes, versioning provides a clear history of changes. This is crucial in many industries where tracking changes and maintaining records is a compliance requirement.




6. Incremental Development: Versioning supports an incremental approach to develpment, you can build and deploy flows iteratively, adding new features or improvements in subsequent versions.




7. Documentation and Understanding: Each version can be accompained by notes or documentation explaining the changes. This is valuable for new team members or when returning to a flow after some time, as it helps in understanding the evolution of the flow.




8. Confidence in Production Deployments: Versioning, coupled with proper testing practices, increases confidence when deploying flows to production, as you know that any chnages can be quickly undone if necessary.



9. Experimentation and Innovation: With the safety net that versioning provides, teams can be more experimental in trying new features or approaches, knowing that they can easily revert to a previous version if needed.





Overall, Versioning is a best practise in software development, including the development of solution cloud flows. It brings structure, safety, and clarity to the process, ultimately leading to more robust and reliable flows.






That's it for today.





I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days
























































Sunday 21 January 2024

{How to} Manage unpublished solution-aware cloud flows using admin APIs on Power Platform

Hello Everyone,








Today I am going to share my thoughts on new feature Manage unpublished solution-aware cloud flows using admin APIs.








Let's get's started.





Managing unpublished solution-aware cloud flows in Microsoft Power Platform using admin APIs involves a sequence of steps requiring administrative privileges. 




First ensure you have necessary permissions typically as a Power Platform or Global Administrator.





Access the Power Platform Admin API, which might involve registering an application in Microsoft Entra ID for authentication.






Use the API to list and identify unpublished cloud flows within a specific environment or solution, 
filtering based on their publication status.





With the API, you can perform various management tasks such as updating exporting, importing or deleting these unpublished flows.






For more advanced management, Consider using Power Platform PowerShell cmdlets for a scriptable interface, allowing for easier automation.






It's crucial to test any management scripts in a non-production environment first and monitor the changes for auditing purposes.







Additionally, staying updated with API changes is important to ensure continuous effective management of your cloud flows.






Currently, Power Automate admin APIs don't fully support the management of solution-aware cloud flows because flows that have never been published(turned on) aren't visible.










Power Automate admin APIs can now fully support the management of solution-aware cloud flows using 
Power automate management connector
Power Automate for Admins Connector
PowerShell for Power Platform Administrators
Power Platform admin center



Admins can see unpublished solution cloud flows, share solution cloud flows and view the ownership cloud flows.





That's it for today.



I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days









































































Saturday 20 January 2024

{Do you know} Make changes in draft mode for solution cloud flows

Hello Everyone,






Today I am going to share my thoughts on new feature related Cloud Flows, can't make changes in draft mode for solution cloud flows.








Let's get's started.






Until now maker's unable to save the cloud flows with erros, and can't save a draft version of a flow.








With the new feature, makers can make changes to the solution cloud flows in draft mode, including when there are errors and publish when changes are complete.







That's it for today.


I hope this helps.


Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days

Friday 19 January 2024

{Do you know} Author custom copilot behaviors with AI plugins

Hello Everyone,






Today I am going to share my thoughts on Authoring custom pilot behaviors with AI Plugins.










Let's get's started.





Authoring custom behaviors for Copilot using AI plugins in Dynamics 365 and Power Platform involves a nuanced process of integration and development.







Firstly, you'll need to understand the intricacies of both Dynamics 365, which offers a suite of business applications, and Power Platform's tools for data analysis, app development, and automation. 




The goal is to identify specific areas where AI can enhance these platforms, such as automating complex workflows, providing predictive insights, or improving customer interactions.




Then, you'll design an AI plugin that seamlessly fits into this ecosystem, adhering to Microsoft's guidelines for security and performance.




This step typically involves leveraging Azure's AI services like Machine Learning or Cognitive Services.




After developing and rigorously testing your plugin to ensure it complements the existing functionalities of Dynamics 365 and Power Platform, you deploy it, carefully monitoring its performance and impact. 







Compliance with data protection laws, thorough documentation, user training, and ongoing support and maintenance are crucial to the successful integration and operation of these custom AI plugins.





This approach not only enhances the capabilities of Dynamics 365 and Power Platform but also tailors them to specific business needs, unlocking new potential for efficiency and innovation.







That's it for today.


I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days















Thursday 18 January 2024

Question Copilot about work order information using natural language

Hello Everyone,







Today I am going to share my thoughts on How to Ask Copilot about Work Order Information using natural language.








Let's get's started.





The below image illustrates a field service technician using natural language to inquire about work order details through Copilot in the Dynamics 365 Field Service App. It captures the essence of modern field service technology, where voice commands simplify the process of accessing and managing work order information.











To ask Copilot about work order information using natrual language in Dynamics 365 Field Service, you would typically use simple, conversational queries. Here are some examples of how you might phrase your questions.






1. For General Work Order Status:

    "Hey Copilot, what's the status of work order 12345?"


      "Can you show me the latest updates on the work order for ABC Company?"





2. For Specific Details:


"Copilot, what parts are needed for the job on Elm Street?"


"Tell me the estimated time of completion for the task assigned to Technician John."



3. For Customer Information:

"I need the contact details for the client on work order 67890."

"What's the service history for the customer at 123 Main Street?"




4.For Scheduling and Assigments:

"Which work orders are scheduled for today?"


" Who is assigned to the emergency repair job this afternoon?"



5. For Reporting Issues or Updates:

"There's a delay on work order 11223 due to part unavailability. Can you update it?"


"Mark the work order 55677 as complete and log 3 hours of labor."






Using Natural Language queries like these allows field service technicians to interact with the system in a more intutive and efficient way, enhancing productivity and reducing the time spent navigating through menus and forms. Copilot's AI Capabilities are designed to understand and process these kinds of requests, making the management of work orders more streamlined and user friendly.







That's it for today.



I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days
























































Wednesday 17 January 2024

What is the significance of the work orders with Copilot in new mobile experience

Hello Everyone,






Today I am going share my thoughts on work orders with Copilot in new mobile experience.









Let's get's started.




Here's an image that visualizes the concept of summarizing work orders using Copilot in the new mobile experience for Dynamics 365 Field Service. It showcases a smartphone displaying the app's inetrface, highlighting the integration of AI assistance for effiecient and modern field service management.













In the new mobile experience, Dynamics 365 Field Service users can now efficiently manage and update work orders using Copilot, an AI-powered assistant. This integration enhances the mobile app's functionality, allowing field technicians to swiftly update work orders through user-friendly interfaces and intelligent suggestions.




Copilot's features like voice commands and AI-driven accurately and access vital information on-the-go.





This modern approach to field service management not only boots productivity but also improves the accuracy and speed of service delivery, directly contributing to enhanced customer satisfaction.





That's it for today.



I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days







































Tuesday 16 January 2024

[How to] Update Dynamics 365 Field Service work orders with Copilot in new mobile experience

Hello Everyone,




Today I am going to share my thoughts on how to update dynamics 365 field service work orders with Copilot in new mobile experience.










Let's get's started.






Here's an image illustration of a field service technician using a smartphone to update work orders in the Dynamics 365 Field Service mobile app with Copilot assistance. The scenario reflects a real world service environment.








1. Set Up Dynamics 365 Field Service on Mobile Devices


Install the Dynamics 365 Mobile App: Ensure that the Dynamics 365 Field Service mobile app is installed on the devices used by your field service team.


Configure Mobile App for Field Service: Customize the mobile app to display relevant information for field technicians including work orders schedules and customer details.



2. Integrate Copilot for Enhanced Assistance


Enable Copilot in Dynamics 365: Make sure that Copilot is integrated and activated within your Dynamics 365 Field Service environment. This might involve configuring settingssin the admin panel.


Train Users on Copilot Features: Educate  your field service team on how to use Copilot for updating work orders, such as using voice commands or AI-powered suggestions for completing fields.



3. Update Work Orders Using Copilot


Access work orders on mobile: Field technicians can open the Dynamics 365 Field Service app and navigate to their assigned work orders.



Use Copilot for Quick Updates: Utilize Copilot AI capabilities for quick updates. For instance technicians can dictate notes or updates to Copilot which then accurately inputs the information into the work order fields.



Capture Images or Videos: If the new mobile experience supports multimedia, technicians can use Copilot to attach images or videos to work orders, enhancing the detail and accuracy of the reports.





4. Leverage Advanced Copilot Features


AI- Powered Diagnostics and Suggestions: Use Copilot analyze issues based on the work order details and suggest possible solutions, parts needed or reference materials.


Real- Time Collaboration: Utillize Copilot for real-time collaboration with other technicians or support staff, potentially integrating with Teams for seamless communications.



5. Sync and Review


Automatic Synchronization: Ensure that all updates made via the mobile app are automatically synced with the central Dynamics 365 system.


Review and Approve: Supervisors or managers can review and approve the work orders updated through the mobile app, ensuring quality and accuracy.





6. Continuous Improvement


Gather Feedback: Reguraly collect feedback from field technicians on the mobile experience and Copilot's effectiveness.


Update and Optimize: Continuously update the system and Copilot features based on user feedback and evolving business needs.


By following these steps, field service organizations can efficiently update work orders using Copilot in the new mobile experience, enhancing the productivity and effectiveness of their field technicians.







That's it for today.


I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days































































Monday 15 January 2024

[How to] Copilot to customize Dynamics 365 Field Service Work Order views for Teams and Outlook

Hello Everyone,




Today I am going to share my thoughts on how to customize work order views for Teams and Outlook.









Let's get's started.




The image visualizes a digital workspace with customized Dynamics 365 Field Service work order views, seamlessly integrated with microsoft teams and outlook. It showcases how these applications can work together, offering a unified and efficient platform for managing work orders and related communication.










Customizing work order views for Microsoft Teams and Outlook using Copilot in Dynamics 365 Field Service involves a blend of Integration and customization strategies.




Here is detailed approach.




Initial Setup and Integration


1. Integrate Dynamics 365 with Microsoft Teams and Outlook:

Access the Dynamics 365 Admin Center.
Enable Integration with Microsoft Teams and Outlook.





2. Configure Teams and Outlook Integration:

In Dynamics 365 Navigate to the integration settings for teams and outlook,

Set up appropriate permissions and select entities(like work orders) for integration.





Customizing Work Order Views


1. Modify work order Entity for Teams and Outlook:

Go to Field Service Settings in Dynamics 365.

Customize the work order entity to ensure it includes relevant fields for Teams and Outlook.




2. Create and Customize Views:

Utilize the Dynamics 365 Customization interface.

Develop specific views for work orders with necessary filters and columns.

Save and publish these custom views.





Utilizing Copilot for Enhanced Customization


1. Engage Copilot for Advanced Customization:

Use Copilot to get suggestions on advanced customizations and best practices.

Apply Copilot's recommendations to enhance the usability and functionality of the work order views.





2. Automate Workflows with Copilot:

Implement automated workflows using Copilot to streamline operations between Dynamics 365 Teams and Outlook.

Ensure these workflows are reflected in the work order views.






Team and Outlook Integration



1. Create Teams Tabs for Work Orders:

In Microsoft Teams, establish dedicated tabs in relevant channels.

Connect these tabs to the Dynamics 365 custom work order views.




2. Synchronize with Outlook:

Make sure the custom work order views are accessible in Outlook via the Dynamics 365 App.





Testing and Training


1. Conduct Testing:

Perform comprehensive tests to ensure functionality and data synchronization across Dynamics 365, Teams, and Outlook.




2. Organize Training Sessions:

Train team members on using the new features and custom views.

Provide resources and documentation for assistance.





Continous Improvement

Regularly update the custom views based on user feedback and evolvin requirements.


Keep an eye on new Dynamics 365 features that could be incorporated.





Through these steps, you can customize work order views in Dynamics 365 Field Service for Microsoft Teams and Outlook, leveraging Copilot for advanced suggestions and automations. This approach aims to enhance collaboration and efficiency in managing work orders within your organization.





That's it for today.



I hope this helps

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days





































































































Sunday 14 January 2024

{How to} Restrict and Protect Customer data on Dynamics 365 Customer Insights.

Hello Everyone,






Today I am going to share new feature benefits of how to protect customer data on Dynamics 365 Customer Insights.








Let's get's started.




Day to day businesses have difficulties to maintain the privacy of customer personal data.



Customer Insights now you can protect the personal data by restricting access and visibility of certain data fields in the Customer Profile, ensuring that data can be used for generating insights that needed across sales, service and marketing.




With this new feature your company can safely use the confidential data more efficiently,so your customers can trust you with data you can then use to better personalize their experience.





Restrict access to data:


1. Customer Profile fields for Dataverse roles can be restricted.


2. Dynamics 365 Customer Insights follows field level security set up in Dataverse, so you dont need to manage these for every Dynamics 365 app separtely.

3. Dynamics 365 Customer Insights marketing professional can continue to build segements based on the restricted fields without seeing the data of the field, such as the email address, in Dataverse and in Customer Insights.

4. Users can continue to use the fields to generate segments, measures and other insights or create personalized journeys and contents, however they will not see any data in those restricted fields.




That's it for today.



I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days
































Saturday 13 January 2024

[Do you know] Move Specific Configurations between environments on Dynamics 365 Customer Insights

Hello Everyone,





Today I am going to share my thoughts on new feature - Move specific configurations between environments on Dynamics 365 Customer Insights.








Let's get's started.



Here is a graphical representation of a user interface for Dynamics 365 Customer Insights, illustrating the process of moving specific configurations between environments.








On Dynamics 365 Customer Insights - Data that might be used on different environments like dev, test, production. 


So maintaining consistency between the environments requires the configurations to be continuously copied across different environments.


Now Customer Insights allows to copy the complete configuration.



With that Customer Insights -Copy Specific configuration like segments and measures between the environment within your tenant.





This allows you to manage more efficiently application lifecycle and test new configurations in lower environment more confidently.


Allowing them to production with automated deployments and Customer Insights pipelines.



Important points:


1. Customer Insights - Data Configurations for segments, measures all others are now solution aware in Dataverse.


2. Copy Solution aware configurations between environments using the solution import/export process in Dataverse.


3. Use Dataverse lifecycle management capabilities to build deployment automation pipelines and source control your configurations.







That's it for today.


I hope this helps.

Malla Reddy Gurram(@UK365GUY)
#365BlogPostsin365Days