Daily ServiceNow change advisory brief in Microsoft Teams

Build an agent that runs on a cron schedule every weekday (Monday through Friday) at 8:00 AM in the user's local timezone. The agent produces a CAB-style morning change brief and posts it to a Microsoft Teams channel. The user should be able to configure the timezone, the Teams team name, and the Teams channel name at install time.

When the agent fires, it should use the ServiceNow List Change Requests action to pull every change request whose planned_start_date falls inside today's window (from 00:00 to 23:59 in the configured timezone). By default, restrict to changes in the Scheduled or Implement states, but let the user override which states are included. Request the fields needed for the brief, including number, short_description, risk, type (especially the emergency flag), state, approval, planned_start_date, planned_end_date, assignment_group, assigned_to, cmdb_ci, and sys_id so deep links can be built.

Then the agent should compose a single formatted message that contains: a one-line headline with the date and total change count; a High and Emergency Risk section that lists each high-risk or emergency change with its change number, planned window in the configured timezone, implementation owner (assigned_to or assignment_group), affected configuration item(s), and a one-sentence summary derived from the short description and implementation plan; a Moderate Risk section in a more compact format; a Low Risk section as a simple bullet list; a Conflicts section that flags any pair of changes whose configuration items overlap and whose planned windows overlap; and an Approvals section that lists any change in today's window whose approval field is not 'approved'. Every change reference should be a deep link back to its ServiceNow record using the user's instance URL and the change request sys_id.

Post the resulting brief as one message to the configured Microsoft Teams channel using the Create Channel Message action. If there are zero changes scheduled for the day, the agent should post a short 'No changes scheduled for today' message so the channel knows the brief ran successfully.

Conflict detection is plain logic on the returned record set: for each pair of changes scheduled today, compare their cmdb_ci values and check whether their [planned_start_date, planned_end_date] intervals overlap. Both members of any overlapping pair should appear in the Conflicts section with a short explanation of which configuration item collides and during which window.

Format the Teams message with clear section headings, bold change numbers, and tight bullet structure so the on-call engineer and the change advisory board can scan it in under a minute. Do not include any internal ServiceNow sys_ids in the visible copy, only in the deep links.