Title: Validate AzureRmAlias removal impact for Emerging DB pipelines
User Story
As a developer, I want to validate the recent pipeline changes related to Enable-AzureRmAlias removal, so that we can confirm there is no impact on Emerging DB shared scripts, modules, or pipeline execution.
Background
Changes have been implemented to remove legacy Enable-AzureRmAlias usage and AzureRM module dependencies from common PowerShell scripts. Since these updates touch shared components, validation is required from the Emerging DB side before release sign-off.
Acceptance Criteria
Hi Hila, Vaishnavi,
Thanks Vaishnavi for the quick chat and for agreeing to discuss this further.
Setting up this call to discuss the LM9 validation inputs shared by Hila and to align on the next steps.
Agenda:
Thanks,
Nikhil
I can read most of it. Some parts on the far right are cut off/unclear, so I’ve marked them as [text cut off / unclear].
Below is a high-level structure to illustrate what I mean. This still needs work. I’ve included some numbers that I have handy and placeholders (XX) where I don’t have them.
He has 2 major roles:
Stepped up as a Scrum Master for the Emerging Database pod, which delivers the Redis Cache and Cosmos DB products. He drives agile execution across epics, improving delivery predictability and achieving a XX% increase in sprint velocity or reduction in cycle time. He ensures effective prioritization and alignment to organizational goals, combining technical expertise with delivery leadership to drive measurable outcomes at scale.
BCM automation — how many hours of manual effort avoided, feedback from BCM and number of app teams that showed appreciation.
One of the pioneers for the Smart Ticket Handler, which used AI and machine learning, Reinfer and Nucleus, to classify user-raised incidents and provide automated responses and resolutions. This resulted in a 40% reduction of user-raised incidents for Oracle.
Owned the actions for major platform migrations including Netcool to BigPanda and IPCenter to Amelia, successfully transitioning 100+ automations while ensuring continuity and alignment with new platforms.
Other automations in Amelia.
Successfully onboarded 400+ Oracle databases to LGTM. LGTM is one of the key dependencies for the re/write program, which is a major, GEB-level transformation initiative.
Drives the remediation and resolution of deployment issues for Oracle through his technical knowledge and effective collaboration with stakeholders such as Automation Services and WMPC CTO.
Contributes to the engineering discussion for the Postgres database exporter package that will enable the collection of metrics from Postgres databases.
Created several ServiceNow reports which improve visibility on open incidents, problems, service requests, and changes. Led to a XX% reduction in unassigned incidents during APAC shift hours.
Created a backup reporting dashboard for Oracle that was used by the team globally, resulting in a XX% increase in successful backup completion.
Authored over XX Assist portal articles and forms, which were integrated into the Smart Ticket Handler.
Led the planning and execution of more than XX major APAC BCM events for databases. Partnered with BCM teams and stakeholders to validate readiness, coordinate execution, and ensure successful completion of events.
Flawless execution of patching for critical XX Oracle and Postgres databases, including Mobile Pass, etc.
In addition to using this space to provide examples of how he demonstrated accountability with integrity, collaboration, etc., use this space for the culture and technical achievements beyond UBS.
Oracle ACE — Being an Oracle ACE is widely regarded as prestigious in the tech industry. It is a global recognition initiative by Oracle that honors individuals who demonstrate exceptional expertise and consistently share their knowledge with the broader community.
(lifted this from Google)
Gold Certified Engineer
AI Citizen — please confirm
UBS Stack Overflow contributor — answered XX number of questions and awarded XX badges
He has an Oracle blog
Was he part of the Hackathon year where you guys placed in the semi-finals?
Enumerate all the charity and community events that he’s led, joined, or contributed to.
Hi All,
A quick clarification on the earlier communication regarding the Cosmos DB CMK / Key Vault remediation.
The email was sent to a wider audience for awareness and visibility. However, action is required only for Cosmos DB accounts using Customer-Managed Keys where remediation/migration is still pending.
If your Cosmos DB account has already been migrated/remediated, or if this change is not applicable to your setup, no further action is required from your side.
For accounts where remediation is still pending, please review the shared guidance and proceed with the appropriate remediation option before the communicated deadline.
Thanks for your understanding.
Regards,
Emerging Databases Team
Use these prompts directly in Teams Copilot.
Type:
Summarize the discussion so far and list any blockers, open questions, decisions, and action items mentioned.
For Scrum/refinement/planning calls, use:
Summarize the discussion so far. Identify any items that need clarification, risks/blockers, ownership gaps, and follow-up actions.
For vendor/Microsoft calls, use:
Summarize the discussion so far. Capture any commitments, dependencies, pending answers, owners, and expected timelines.
Type:
Create a closing summary with key decisions, action items, owners, due dates, blockers, and next steps.
For Scrum Master use, this is even better:
Prepare a clear meeting closure summary. Include: decisions made, action items with owners, unresolved blockers, dependencies, due dates, and topics to carry forward.
Then you can say verbally:
Before we close, I’ll quickly confirm the decisions, action items, owners and next steps so we are aligned.
A very strong final prompt for your role:
Generate professional meeting notes from this call with sections: Summary, Decisions, Action Items, Owners, Blockers, Dependencies, Due Dates, and Next Steps.
Hi, my name is Nikhil Kotak. I have been with UBS for more than nine years, and I currently work as a Site Reliability Engineer for databases. I also support the Emerging Database team as Scrum Master.
One achievement I am especially proud of is contributing to reliability and delivery maturity in the Emerging Database space. Emerging Database involves evolving technologies, external dependencies and new ways of working, where clarity, ownership and structured execution are very important. As Scrum Master, I help convert unclear topics into trackable actions, surface blockers early, align engineers, Product Owners, Reliability Owners and vendor teams, and keep delivery focused on outcomes.
Alongside this, I am proud of my contribution to PostgreSQL reliability since PostgreSQL was introduced as a strategic database platform within the bank. I conducted brown bag sessions with stakeholders across APAC and EMEA to build awareness, confidence and alignment. I also independently designed PostgreSQL BCM automation, converting manual checks, risk controls and evidence collection into a repeatable automated process, reducing manual effort by around 95%.
I have also been involved in ML and AI-led automation initiatives, using intelligent automation to reduce repetitive manual ticket resolution and improve operational efficiency by around 22% over the past year.
What motivates and inspires me at UBS is the scale, trust and impact of the work. I am proud to be recognized internally through CE Gold, externally by Oracle as an ACE Pro, and to contribute to UBS volunteering events. These experiences motivate me to keep growing, sharing knowledge and contributing beyond my immediate role.
Overall, I am proud to contribute through reliability, automation, collaboration, volunteering and continuous improvement.
Hello Friends! I am aliena part time blogger from Bihar. I am a student and I manage my study as well as my blog. I am 14 years old and I want to help those people who really want to do something on internet.
Copyright © 201. Metro UI Theme. Designed by: Templateism
