There are many different approaches when it comes to prioritizing the vulnerabilities which need addressing with urgency. Any information or guidance to help you make better informed decisions can be critical but how can you stay informed? Leveraging all the information sources available to you can be the difference and allow you to be proactive when trying to protect your organization.
One useful feed is offered by CISA (Cybersecurity & Infrastructure Security Agency) who works with partners to defend against today’s threats and collaborate to build a more secure and resilient infrastructure for the future. The Known Exploited Vulnerabilities (KEV) Catalog is a curated list maintained by CISA. It identifies vulnerabilities that have been actively exploited in the wild, posing significant risks to organizations and individuals. The catalog aims to enhance cybersecurity by providing timely information on these vulnerabilities, enabling proactive mitigation efforts.
Key features of the KEV Catalog include:
Identification: Lists vulnerabilities that are confirmed to be exploited.
Details: Provides technical details, including affected products and versions.
Mitigation: Offers guidance on how to address and remediate the vulnerabilities.
Updates: Regularly updated to reflect new threats and exploited vulnerabilities.
The KEV Catalog serves as a critical resource for cybersecurity professionals, helping them prioritize patching and defense strategies to protect against known threats.
The feed is designed to help organizations stay informed about vulnerabilities that have been exploited in the wild. It is part of CISA’s efforts to defend against current threats and build a more secure and resilient infrastructure for the future
Workflow overview
The automated CISA feed solution addresses prioritization challenges by streamlining the process of vulnerability management. This solution checks the latest CISA feed every 24 hours and queries the CVE findings against devices within Microsoft Defender for Endpoint. Security Copilot then checks for remediation actions and enriches the description, providing a comprehensive overview of the vulnerability.
Figure 1: Example of the email output from the Logic App
Key benefits of the Logic App include:
Automated Updates: The Logic App automatically retrieves the latest CISA feed, ensuring that analysts have up-to-date information without manual intervention. This eliminates the need for manual checks and reduces the risk of missing critical updates.
Device Vulnerability Assessment: It queries the CVE findings against devices within the organization, identifying which devices are vulnerable to the reported CVEs. This targeted approach allows analysts to focus on the most critical vulnerabilities affecting their specific environment, enhancing the efficiency of the remediation process.
Remediation Insights: Security Copilot provides detailed remediation actions, helping analysts understand the steps needed to mitigate the vulnerabilities. By enriching the description with actionable insights, it simplifies the decision-making process and accelerates the implementation of security measures.
Email Notifications: An email with the findings is sent to a designated mailbox, allowing for easy review and follow-up. This ensures that all relevant stakeholders are informed promptly, facilitating coordinated responses and continuous monitoring of the organization’s security posture.
Figure 2: Screenshot of the CISA Logic App
Click here to get started and install the Logic App today.
Conclusion
To prioritize effectively, gather all necessary information for informed decisions. While the Logic App CISA workflow is one approach, other methods may better suit your organization. Function Apps can enhance decision making by automating and streamlining security operations with integrated tools and processes. The Security Copilot GitHub repository offers AI-powered solutions using machine learning and natural language processing to improve security. These tools help identify vulnerabilities, predict risks, and implement protective measures. Check it out!
Microsoft Security Copilot is a SaaS-based, AI-powered cybersecurity solution that uses generative AI to empower defenders to protect at speed and scale of AI. Integrating Security Copilot with other SaaS platforms is generally straightforward thanks to native cloud-to-cloud connectivity. This includes native cloud-to-cloud integration with Splunk Cloud, now part of Cisco.
The Security Copilot plugin for Splunk also supports on-premises and self-hosted VM deployments of Splunk; however, additional steps are required to enable secure and reliable communication in these scenarios.
This blog walks you through how to integrate Security Copilot with non-SaaS editions of Splunk using Microsoft Entra ID Application Proxy and Azure Application Gateway with Web Application Firewall (WAF). This setup ensures that your Splunk instance remains protected behind enterprise-grade security controls while still being accessible to Security Copilot for log analysis and threat investigation.
While this guidance is specifically for Splunk the same general principles can be applied to integrate other on-prem solutions with Security Copilot.
Solution overview
In this blog post, we illustrate how to securely integrate Microsoft Security Copilot with Splunk in two common scenarios:
When your Splunk instance is already running within an Azure Virtual Network (VNet).
When your Splunk instance is deployed on-premises but you already have network connectivity to an Azure VNet through VPN or ExpressRoute.
If these conditions are not met—for example, if your Splunk deployment is fully isolated on-premises without connectivity to Azure—it is still possible to securely expose your instance to Security Copilot by using a reverse proxy hosted on-premises instead of Azure Application Gateway. However, that approach is outside the scope of this blog.
The solution presented here relies on a combination of Microsoft Entra ID Application Proxy and Azure Application Gateway with Web Application Firewall (WAF) to create a secure, controlled communication channel between Security Copilot and your Splunk instance.
Entra ID Application Proxy is used to publish the Splunk REST endpoint in a secure manner. This ensures that the Splunk instance is not directly exposed to the Internet and that no inbound ports need to be opened on your firewall.
Azure Application Gateway, equipped with WAF, acts as a reverse proxy that enforces access controls based on source IP addresses. It ensures that only traffic originating from the known Security Copilot egress IPs is allowed to reach the published Splunk endpoint. Additionally, WAF allows you to enforce protections such as the OWASP Top 10, Bot Protection and custom rules adding another layer of defense.
This approach is applicable not only for Splunk instances hosted in Azure, but also for self-hosted VM deployments running on other public clouds such as AWS or GCP, as long as they are reachable via a secure VNet-integrated path.
Below is a high-level view of the architecture:
Splunk hosted on AzureSplunk instance deployed on-premises with network connectivity to an Azure VNet through VPN or ExpressRoute
Step by step deployment guide
The following sections describe the procedures for configuring Microsoft Entra ID Application Proxy and Azure Application Gateway to enable secure integration between Security Copilot and your Splunk instance.
⚠️Important: While the guidance provided outlines a reference architecture, please make sure to adapt all configuration steps to reflect your actual network topology and IP address space. Specific settings such as subnet ranges, routing paths, and firewall rules should align with your organization’s infrastructure design and security policies.
Entra ID Application Proxy setup and configuration
Download and Configure the Connector Service
To enable secure connectivity between Security Copilot and your on-premises or self-hosted Splunk instance, begin by setting up the Entra ID Application Proxy connector:
Download the connector from the Azure Portal: go to https://portal.azure.com → Entra ID → Application Proxy.
App Proxy Connector download
Ensure your network environment is properly configured for outbound connectivity. Refer to Microsoft’s documentation for detailed prerequisites and firewall rules.
The connector must be installed on a Windows Server 2012 R2 or later.
Once installed successfully, the connector establishes a secure outbound communication channel with Azure. You can verify its status under the Health Status section in the portal.
Connector health status
Configure an Entra ID Application for Splunk
The next step is to publish your Splunk instance as an app via Application Proxy. This allows Security Copilot to securely invoke Splunk’s APIs, which are exposed on the default management port 8089.
Note: Ensure that the splunkd service is configured with a valid SSL certificate. The connector requires HTTPS for communication.
In the Application Proxy section, click on “Configure an app”.
Configure an app
Fill in the relevant fields. Under the Pre-authentication section, select “Passthrough“. Since the Security Copilot plugin supports either API Key Authentication or Basic Authentication, it cannot perform Microsoft Entra ID authentication. Therefore, authentication must be handled directly by Splunk.
Configure an app
Important: To add an additional security layer and restrict access only to Security Copilot’s egress IP addresses, a custom WAF Policy will be configured on the Application Gateway, as described in the following section.
Once configured, the app will be visible under Entra ID → App registrations.
Splunk App registration
You can test the application by navigating to the external URL defined during setup.
Note: Although Splunk listens on port 8089, Application Proxy exposes the service externally over port 443 (HTTPS).
Licensing Requirement: Entra ID P1 licenses or higher are required to use Application Proxy.
Application Gateway and WAF Configuration
You can use the Azure Portal wizard to create and configure the Application Gateway with the following steps:
Navigate to Create a resource > Networking > Application Gateway.
Select the appropriate Resource Group and Azure region.
For Tier, choose WAF V2.
If you already have a WAF Policy, select it. Otherwise, you can create one later using the configuration guidance provided in the next section.
Choose the dedicated subnet (e.g., subnet-appgw) for the Application Gateway instance.
Create Application Gateway
Configure the Frontend IP
Select Private as the frontend IP type.
Assign a static private IP address from the selected subnet. This IP will serve as the entry point for requests coming from Entra ID Application Proxy.
Fronted configuration
Add the Backend Pool
Add your Splunk Search Head as a backend target.
This can be either:
A VM running in the same VNet as AppGW, or
A Splunk instance hosted on-premises, reachable via VPN or ExpressRoute.
Add backend pool
Configure Routing Rules
Under the Configuration tab, add a Routing Rule:
Create a Listener and bind it to the private frontend IP you configured in step 2.
Upload your Splunk instance’s TLS certificate in PFX format to enable HTTPS.
Set the backend protocol to HTTPS and the port to 8089, which is the default for Splunk’s management and search APIs.
Add routing rule – listener
Add routing rule – backend
Tags (optional)
Add tags as needed for resource classification, billing, or automation purposes.
Review and Create
Review your configuration and create the Application Gateway.
review and create
Once deployed, the Application Gateway will serve as a secure intermediary, ensuring that only requests from the known Security Copilot egress IPs reach your Splunk instance, and that all communication is encrypted and inspected by WAF.
WAF Policy configuration
Create a WAF Policy, associate it with the Application Gateway, and configure a custom rule as follows to allow traffic only from the Security Copilot egress IPs. Note: Since the traffic is proxied through Entra ID Application Proxy, the source IP check must be performed on the X-Forwarded-For header.
WAF policy
Configuring your Splunk plugin in Security Copilot
Navigate to the Splunk plugin and select Setup
Plugin set up
Choose your preferred authentication method (API Key) recommended
Plugin authentication
Enter the external url generated by Entra ID App proxy and click save
Plugin settings
Conclusion
By leveraging Microsoft Entra ID Application Proxy and Azure Application Gateway with Web Application Firewall (WAF), you can securely connect on-premises or self-hosted Splunk instances to Microsoft Security Copilot – enabling seamless log analysis and threat investigation without exposing Splunk to the internet. This approach extends Security Copilot’s reach beyond SaaS applications, broadening the context needed for effective investigations across hybrid environments.
We’re thrilled to announce the public preview of Process Map in Power Automate, a significant advancement for process-centric observability at scale. This feature is seamlessly integrated into the Automation Center, your hub for end-to-end automation monitoring and management in Power Automate.
What is the Process Map?
The Process Map is designed to enhance process-centric troubleshooting and monitoring in Power Automate by providing increased visibility and efficiency. It offers a detailed, end-to-end view of a process that’s managed by a parent orchestrating flow, showing all of the associated child and desktop flows. The map also recognizes structural flow elements, such as conditions, and displays flows that didn’t execute due to specific conditional logic or upstream errors. This is critical for understanding how a problem in one part of the process can affect other parts and assists in taking appropriate countermeasures to address issues.
Key benefits:
Accelerated troubleshooting: Quickly identify and resolve issues with an end-to-end, process-centric view that includes contextual information on runs, connections, and design-time aspects.
Comprehensive visibility: Gain full transparency into your automation processes, including flows that were skipped or missed due to conditional logic or upstream issues.
Enhanced impact analysis: Understand and analyze how issues affect the entire process, facilitating faster recovery and implement effective countermeasures.
Stronger collaboration: End-to-end process visibility enables faster, context-rich communication with impacted teams, accelerating recovery and driving continuous improvement.
Key features
Runsview: Displays the main flow run that orchestrates the process and its child runs, enabling users to track execution, identify issues, and optimize processes.
Overviewview: Provides a design-time process hierarchy view with connected subprocesses, offering quick insights and serving as the future home for aggregated process data and configurations.
Runs tab integration: We’ve enhanced the flow runs page with new run row hover options. New icons let you create or view process maps for the selected process run and its child runs.
How to get started
This feature is being rolled-out now and you can test it today in the US preview region. Further details are available in the Process Map documentation.
Setting Edit Rights in a SharePoint Site – Approach with Caution!
Scenario: A marketing team is using a SharePoint site to collaborate on a critical presentation for an upcoming product launch. The document contains sensitive information such as pricing strategies and competitive analysis. All team members are given Edit rights to the site to encourage seamless collaboration. The site includes various document libraries and multiple automation points using document libraries and lists.
Incident: One of the team members, Alex, accidentally deletes a slide that outlines key metrics for the presentation while editing the document late at night. Unaware of the deletion, Alex saves the document and uploads it back to the SharePoint site.
The next morning, during a meeting with stakeholders, the team presents the incomplete document. The missing slide causes confusion, leading to miscommunication about the product’s goals. Additionally, retrieving the deleted content becomes time-consuming, as the team needs to check previous versions and piece together the missing information.
Impact:
Reputation Damage: The team appears unprepared and unprofessional in front of stakeholders.
Loss of Time: Valuable time is wasted trying to recover the deleted content and address the errors.
Potential Financial Implications: Miscommunication about product goals could lead to misaligned strategies, affecting the launch’s success.
Lesson: This scenario highlights the risks of granting Edit rights broadly. It underscores the importance of assigning Edit rights selectively and implementing controls such as versioning and approval workflows to safeguard critical documents
SharePoint is a powerful collaboration tool that allows teams to efficiently manage documents, share information, and work together on projects. However, when configuring access permissions, granting Edit rights indiscriminately can lead to several risks and challenges. Below are the key reasons why setting Edit rights in a SharePoint site should be approached with caution:
Risk of Accidental Deletion or Modification
When users have Edit rights, they can modify or delete files, folders, or even site components. While this level of access may be necessary for certain roles, it can lead to accidental changes or deletions. This may result in loss of critical information, disrupted workflows, or significant time spent restoring deleted items.
Compromised Data Integrity
Edit permissions allow users to alter content, which can introduce errors or inconsistencies. Without proper oversight, documents and information may lose their accuracy or become outdated due to untracked edits. Maintaining data integrity is essential, especially for projects or systems that rely on precise and consistent information.
Lack of Version Control Awareness
While SharePoint does offer versioning capabilities, users with Edit rights may not always use them correctly. Overwriting files or failing to save new versions can make it challenging to recover previous iterations of a document. This can be particularly problematic in scenarios where collaboration requires retaining a history of changes.
Security Risks
Granting Edit rights increases the risk of sensitive information being exposed or manipulated. Users may unintentionally or deliberately share content with unauthorized individuals, resulting in data breaches or non-compliance with organizational policies. Limiting permissions to read-only for most users helps safeguard confidential information.
Disrupted Site Structure
Users with Edit rights can modify site components, such as views, lists, or libraries, potentially disrupting the site’s structure and functionality. Such changes can create confusion among other users and hinder productivity.
Overcomplication of Permissions Management
If Edit rights are granted broadly, managing permissions becomes more complex. Revoking access, addressing security incidents, or troubleshooting issues can become tedious, especially if the site has a large user base.
Recommendations
To mitigate these risks, organisations should consider the following best practices:
Adopt the Principle of Least Privilege: Grant the minimum level of access necessary for users to perform their tasks effectively;
Use Read-Only Access for Most Users: Reserve Edit rights for a select group of individuals who truly need this level of control;
Implement Workflow Approvals: For edits to critical documents, use workflows to ensure changes are reviewed before implementation;
Regularly Audit Permissions: Periodically review user access to ensure it aligns with their current roles and responsibilities.
By carefully managing Edit rights in SharePoint, organisations can enhance collaboration while minimising risks and maintaining the integrity of their data and systems.
Power Automate continues to evolve, bringing new security features to help organizations protect their data and automate intelligent processes more securely by design. Here are some of the latest enhancements:
Protect Identities and Secrets with credential management
Desktop flow connection credentials with Azure key vault and CyberArk secrets: Power Automate now supports storing connection credentials securely in Azure Key Vault (AKV) or CyberArk. This ensures that passwords are encrypted and managed securely, reducing the risk of unauthorized access. This feature includes support for automatic connection updates at runtime (like when a password rotation occurs).
Certificate-Based Authentication with MFA (Public preview): To further enhance security, Power Automate now supports certificate-based authentication in desktop flow connections. This passwordless solution adds an extra layer of security, meeting multi-factor authentication (MFA) requirements for attended as well as unattended scenarios. This feature is available from Power Automate for Desktop Build 2410.
Credentials for Desktop flow actions (Public preview): For desktop flows, Power Automate allows the use of credentials directly within flow actions. This ensures sensitive information is handled securely, not stored in scripts or logs, and accessible only to authorized users. This feature is available from Power Automate for Desktop Build 2411.
Network isolated, private environments with customized network security measures, such as Network Security Groups and firewalls, to control and monitor traffic.
Integration with on-premises networks through VPN or ExpressRoute where access to on-premises resources is necessary for RPA workloads.
Network Level Authentication (NLA) is a security measure that mandates user authentication prior to the establishment of a remote desktop connection. This feature assists organizations in mitigating the risk of unauthorized access by ensuring that only authenticated users can initiate a remote session, thereby protecting against vulnerabilities associated with the authentication process.
This feature is now supported when running unattended workload using a MS Entra ID account on a Microsoft Entra joined or hybrid device.
These new security features make Power Automate an even more robust tool for automating intelligent processes while maintaining a high level of security. By protecting identities and secrets, safeguarding networks, and monitoring for threats, organizations can confidently leverage Power Automate to drive efficiency with hypermation.
In today’s business environment, streamlined workflows and reduced manual tasks are essential. Microsoft AI Builder brings the power of advanced automation to routine processes like email handling, document processing, and image management, helping businesses run smarter and more efficiently. With new capabilities, including multi-modal content processing, structured JSON outputs, flexible model selection, Dataverse grounding, and an extensive prompt library, AI Builder elevates agents, apps and automation to the next level of business impact.
Next generation document and image processing with GPT
One of the most game-changing updates in AI Builder is the new multi-modal content processing capability, which allows businesses to handle various data types —including text, document, and images—within a single natural language instruction. This integration greatly simplifies the process of crafting AI actions for intelligent document processing. Unlike traditional machine learning models that require extensive training and expertise, AI Builder’s multi-modal processing can be set up using natural language, and without training data.
Structured JSON outputs now generally available
With AI Builder’s new structured JSON output feature, businesses gain a more deterministic and reliable way to handle generated content. Unlike traditional outputs that might vary in format and structure, JSON outputs are now generated with a consistent predefined schema that you define at design time, ensuring that every result aligns precisely with expected data formats. This determinism in content generation means your automated workflows will produce predictable, structured data every time, and those results will be readily integrated as variables in your Power Automate workflow for downstream processing. This feature is especially beneficial when integrating AI Builder outputs into other systems, as it reduces the need for additional data cleaning or transformation. Whether feeding data into a CRM, database, or custom application, you can ensure that data is generated in a structured and predictable way.
Dataverse grounding is now generally available
The new Dataverse grounding capability empowers Generative AI models with up-to-date, contextually relevant information from your organization’s own data. By employing Retrieval-Augmented Generation (RAG), AI Builder integrates directly with Dataverse to pull in real-time, business-specific knowledge, giving models a deeper understanding of your unique context.
This RAG-enhanced approach allows AI models to dynamically retrieve and incorporate relevant data from Dataverse during processing, enabling Q&A scenarios with accurate responses that are also highly contextualized to your organization. For instance, models can instantly access customer histories, product information, and up-to-the-minute operational data, enriching outputs with knowledge directly grounded in your business reality.
As part of this feature becoming generally available, the capability has been enhanced to support multiple tables, including tables with large amounts of data records.
Model selection: GPT-4o and GPT-4o Mini
AI Builder offers flexibility in model selection, allowing users to choose between the powerful GPT-4o and the cost-effective GPT-4o Mini. This adaptability enables customization based on specific project requirements and resource considerations.
Prompt library
The prompt library feature provides a collection of pre-designed prompts, serving as templates to expedite the creation of AI models. This resource accelerates development and ensures best practices are followed in prompt engineering. Users can modify templates to suit specific needs, adjusting language, tone, and detail to match organizational standards and requirements. The templates cover key areas like document extraction, data transformation, and content generation, making it easy for users to find the right starting point for their intelligent automation goals.
Use cases to get started
With AI Builder, you don’t need to be a coding expert to leverage the power of AI in your daily operations. By creating prompts that can extract information from documents, classify emails, and even analyze images, you can empower your team to work smarter, not harder. AI Builder works hand-in-hand with other Power Platform tools like Power Automate, Copilot Studio and Power Apps, enabling users to create intelligent workflows and applications that are customized to meet the needs of any business.
For example, let’s say your team frequently processes customer inquiries. Using AI Builder and Power Automate, you can design a workflow that analyzes the content of incoming emails, categorizes them by urgency or topic, and even suggests responses. This not only saves time but also keeps communication consistent and efficient. By setting up this automated flow, businesses can stay on top of customer interactions and ensure timely responses.
Are you ready to bring AI to your organization?
The AI Builder Documentation provides a comprehensive guide on setting up AI Builder, configuring models, and integrating it with tools like Power Automate and Power Apps. For step-by-step tutorials, the Microsoft Learn AI Builder Learning Path is an excellent place to start. It covers everything from foundational concepts to advanced use cases, helping users of all levels become proficient in leveraging AI Builder to automate and optimize workflows.
The latest AI experiences in Power Automate are redefining the boundaries of what is possible in enterprise automation—transforming how we optimize and manage business processes to achieve more. Developers can now create advanced automation faster, business analysts can quickly extract, analyze, and optimize critical processes, and IT administrators can seamlessly manage and govern automation at scale. Copilot in Power Automate makes it faster to build solutions that save valuable time and reduce costs, thereby achieving business outcomes. Step into the future with the Power Automate advanced, enterprise-grade intelligent automation solutions.
Build advanced, reliable automations faster with AI
Developers are key to business process innovation. In Power Automate, it is now possible to build automations that utilize AI within cloud flows using generative actions, easily use natural language to create expressions for flows with Copilot for expressions, and incorporate document processing into workflows with next-generation document processing. These features enhance developers’ ability to deliver solutions efficiently and effectively.
Introducing next-generation document processing with GPT
Efficient document management is vital for smooth operations and timely decisions, but traditional AI models require lengthy training and frequent updates. With GPT-4-powered document processing, now available in public preview, you can use natural language to extract and process unstructured data from documents like invoices, medical results, or emails. This next-gen tool handles multi-modal content, automating email, document, and image processing for improved productivity. For makers who want to blend in pro-code or gain greater control, we’ve added the ability to structure outputs using JavaScript Object Notation (JSON) directly inline. Makers can combine multi-modal content with enterprise knowledge from Microsoft Dataverse in their prompts. This feature enables makers to quickly deploy document and image processing directly into existing workflows using natural language instructions.
Transform your automation processes with generative actions
Generative actions allow you to add AI-powered steps to your cloud flows, letting AI reason over enterprise guardrails provided in unstructured content format such as documents and PDFs, and decide the best course of action for complex tasks. For example, with generative actions you can automate conditional approvals based on the content of incoming emails and company policies. This feature, currently in the Early Access Program, is coming soon to public preview, when you will be able to create, edit, test, and run generative actions all from within the cloud flow designer.
Create and edit expressions faster with Copilot
Copilot for expressions, now in public preview, is designed to assist developers and makers in creating or editing complex expressions using natural language. By simply describing what you want to build and referencing the dynamic data in the flow, Copilot translates your prompts into specific expressions in your Power Automate flow, speeding up development and reducing manual coding time.
Monitor and manage at scale with new automation center
Automation center, now generally available, is a central hub for efficient monitoring and troubleshooting experiences for automation processes across Power Automate at scale. The automation center provides comprehensive visualizations that enable you to monitor the health of your automations, quickly detect issues or trends, and troubleshoot problems more efficiently.
Whether you’re a developer, operator, Center of Excellence team member, or business analyst, the automation center provides a centralized view of all automation activities. Now generally available, it features a user-friendly interface with dashboards that show recommendations, the health status of work queues, and desktop flow activity. Additionally, new views for execution logs, performance metrics, and integrated agents are now available in public preview.
To learn more and to get started, read our Automation center documentation.
Improve robotic process automation (RPA) reliability using repair with Copilot
Repair with Copilot, now in public preview, simplifies resolving user interface (UI) control issues in both attended and unattended RPA with Power Automate for desktop. By proactively providing solutions to common automation issues, such as notifying the right person in the automation center, repair with Copilot reduces downtime for RPA scenarios.
Example of using repair with Copilot for unattended RPA:
Example of using repair with Copilot for attended RPA:
Start your journey into a new era of automation and AI
Are you ready to bring your organization into the future with the latest AI capabilities in Power Automate? Get started with a free trial or compare plans, join our sessions below at Microsoft Ignite 2024, and read about other exciting announcements for Microsoft Power Platform.
Power Automate
Find the right low-code automation plan for your business.
