VNode ITeSBook
VNode ITeS Our people

Professional profile · VNode ITeS

Parveen KR

Founder & Principal Consultant

Frontier Transformation Engineer · Agentic AI Business Solutions Architect · Microsoft Certified Trainer

Consulting, practical engineering and technical training for leadership, management, business and technical teams.

Forward Deployed Engineering (FDE): customer discovery, solution engineering, evaluation and handover.

I have worked with leadership and management teams, business teams and technical practitioners across training, consulting and capability development. The starting point varies: leaders may need to evaluate an adoption decision, managers may need to prepare their teams, and practitioners may need to build, test or improve a solution.

Across 22+ years, my work has connected technical subjects with the decisions and practical work people are responsible for. For each engagement, we agree the intended outcome, the depth required and how the work will be reviewed.

Microsoft Certified Trainer since 2012
Parveen KR, Founder and Principal Consultant at VNode ITeS
Founder-led deliveryParveen KR

Training · Consulting · Applied labs

22+

Years across training, consulting
and capability development

50,000+

Professionals enabled
across Parveen’s career

2,500+

Sessions delivered
across Parveen’s career

International delivery

Programmes delivered to client teams across countries.
Across Parveen’s career

01 / Working with me

How I can support your team.

I lead VNode ITeS engagements across consulting, scoped engineering and technical training. I also work with vendors and delivery partners on agreed assignments, with the subject, audience, responsibilities and practical requirements reviewed before we begin.

Consulting and advisory

Clarify the requirement, review options and agree architecture, governance and implementation boundaries.

Scoped engineering

Agree a bounded piece of application, integration, data or agent work, including testing and handover expectations.

Technical training and partner delivery

Prepare audience-appropriate learning, demonstrations and practical exercises for direct clients or delivery partners.

02 / Expertise

What we can work on together.

The subject matters, but so does the starting point. We agree what your team already knows, what they need to do next and how much practical work the engagement should include.

01

AI, Copilot and agents

Help your team work with Copilot and agents, check the answers they receive and decide where human review is needed.

Copilot Studio Apps and Copilot Managed Runtime — Preview. These are separate from Power Apps code apps. Preview topics require an agreed scope and tenant readiness.

Topics and practical work
What we cover
Microsoft 365 Copilot; Copilot Studio agents and workflows using the Microsoft Copilot harness (formerly GitHub Copilot harness); standard-harness agents and agent flows. Microsoft Foundry model selection, knowledge grounding, tools, evaluation and tracing. Workflows, agent flows and Power Automate flows are different experiences.
Who it suits
Leadership and management teams, business users, developers, solution teams and AI practitioners.
The practical work
Review a workflow, check grounded answers, test tool permissions and agree human review points. Feature access, licensing and environment readiness are checked before practical work.
02

Microsoft 365, SharePoint and Teams

Help people use collaboration tools well, while administrators keep sites, sharing and access under control.

Topics and practical work
What we cover
SharePoint sites, pages, lists and document libraries; Teams collaboration for end users; SharePoint administration, permissions and external sharing; agents in SharePoint and their access to permitted content.
Who it suits
End users, site owners, Microsoft 365 administrators and managers responsible for collaboration and adoption.
The practical work
Practise collaboration tasks, review site ownership and sharing, and test agent answers with different user permissions. Agent access depends on supported licensing or pay-as-you-go arrangements.
03

Microsoft 365 development and Graph

Build extensions and integrations around the way people work in SharePoint and Teams.

Topics and practical work
What we cover
SharePoint Framework (SPFx) web parts and extensions; Teams applications and supported SPFx tabs; Microsoft Graph API integration, delegated and application permissions, consent and least privilege.
Who it suits
Developers, solution architects and technical administrators responsible for application access and deployment.
The practical work
Scope an application, call an appropriate Graph endpoint and review permissions. Delegated access combines granted permissions with user access; app-only access uses the application identity and its granted permissions.
04

Data, Fabric and Databricks

Work through how data is collected, transformed and used, with practical attention to quality and access.

Selected Fabric AI integrations and protections remain Preview, including Purview protection capabilities for Fabric data agents. Data-agent availability does not establish availability of every connected feature.

Topics and practical work
What we cover
Microsoft Fabric, OneLake, Power BI, data engineering and lakehouse patterns. Fabric Copilot experiences, Fabric data agents, notebook AI functions and data science/model evaluation. Azure Databricks, Unity Catalog governance and MLflow evaluation for generative AI.
Who it suits
Data engineers, analysts, architects, administrators, and platform teams.
The practical work
Follow data from ingestion through reporting, inspect governed access and compare results with known examples. Notebook AI functions can classify, summarise and extract information; generated outputs still need review. Capacity, tenant settings, region and feature availability are checked first.
05

Azure and application engineering

Connect application code, APIs and cloud services, then review the identity, testing and release decisions.

Topics and practical work
What we cover
Azure architecture and administration, C#/.NET, ASP.NET Core, Python, APIs, identity, integration and CI/CD.
Who it suits
Developers, cloud engineers, DevOps teams, architects, and technical leads.
The practical work
Work in a repository: build an API, handle identity, write tests and review what needs to happen before release.
06

Power Platform and Dynamics 365

Build an understanding of the business process before choosing the application, automation or configuration work.

Topics and practical work
What we cover
Power Apps canvas apps, model-driven apps and code apps; Power Automate, Power Pages and Dataverse. Code apps support code-first web development with platform data connections and governance. Dynamics 365 training and demonstrations across Sales, Field Service, Customer Insights, Customer Service, Commerce, Project Operations and Human Resources; application-specific scope is agreed separately.
Who it suits
Makers, functional consultants, business teams, and application delivery groups.
The practical work
Configuration, customisation, business process flows, security roles and integration exercises. We agree the application and depth first, including whether Customer Insights means Data or Journeys. Check environment enablement and licensing for code apps. Training and demonstrations are scoped separately from production implementation.
Discuss Dynamics 365 training
07

Data governance, identity and AI security

Review who can access data, how it is used and which controls need to be in place before extending an AI workflow.

Topics and practical work
What we cover
Microsoft Purview Data Map and Unified Catalog, information protection and sensitivity labels, data loss prevention (DLP), retention and audit. Microsoft Entra ID, Conditional Access, least privilege and workload identities. AI data handling, grounded-source access, tool permissions and human approval boundaries.
Who it suits
Governance and security teams, administrators, architects and data owners; leadership and management teams reviewing responsibilities and risk.
The practical work
Map data ownership and access, review protection policies and test permitted and denied actions. A catalogue does not grant access to the source data. Purview controls vary by application and licence; security work does not itself establish regulatory compliance.
08

AI-assisted software development

Use coding assistants in a real repository while keeping requirements, tests and review in the developer’s hands.

Topics and practical work
What we cover
GitHub Copilot, Cursor, Claude Code and OpenAI Codex in repository-based development.
Who it suits
Developers, technical leads and application teams.
The practical work
Use VNode application work and demonstrations to examine debugging, refactoring, tests and code review. Suggestions still need to be checked against the requirement.
09

Learning design and mentoring

Shape the learning around the audience, prepare useful exercises and help people carry the work forward.

Topics and practical work
What we cover
Needs analysis, participant readiness, curriculum design, applied labs, assessments and mentoring.
Who it suits
Learning partners, managers, delivery teams and mixed technical/business cohorts.
The practical work
Prepare the labs, check what learners already know and adjust the exercises to the work they need to do next.

Forward Deployed Engineering (FDE)

Forward Deployed Engineering connects customer discovery with hands-on solution engineering. My training covers how to understand a workflow, agree a useful scope, work with data and integrations, evaluate the result and prepare a clear handover.

Explore FDE training
Delivery formats
VirtualOn-siteHybridCorporate cohortsFocused workshopsBootcampsCertification-alignedCustom labs

03 / Engagement review

Evaluation and quality control

Before agreeing an engagement, I review the outcome, audience, subject depth and practical requirements. We use that conversation to agree the scope, delivery approach and responsibilities.

01

Scope review

Understand the business context, audience, intended outcome and boundaries.

Is the intended outcome clear enough to agree the scope?
02

Capability match

Review the subject depth, audience level and delivery expertise required.

Does the expertise match the subject and audience?
03

Delivery design

Agree the agenda or work plan, practical exercises, review points and oversight.

Will this delivery design support the agreed outcome?
04

Onboarding readiness

Confirm dates, access, responsibilities, communication and escalation arrangements.

Are access, responsibilities and arrangements ready?

Quality controls

  • Check starting knowledge before agreeing the final agenda.
  • Confirm lab access and platform permissions before delivery.
  • Choose the trainer for the subject and audience, not just an open date.
  • Keep founder-led oversight of content and delivery quality.
  • Discuss any change of scope or trainer before it is offered.
  • Bring in additional trainers only after scope, quality and supervision are agreed.

Information needed for evaluation

Business context
What the organisation needs to do and what is difficult today
The people
Leadership, management, business or technical audience; roles, starting knowledge and group size
Dates and time zone
Preferred window, daily timing, and scheduling constraints
Delivery mode
Virtual, on-site, hybrid, workshop, cohort, or bootcamp
The outcome
What participants should be able to do afterwards
Practical setup
Accounts, permissions, sample data and any security restrictions

Before we commit: you should know what is included, who is delivering it, what needs to be ready and how we will review the work.

Kriya AI · Microsoft Learn