Meeting Date:

Topic / GitLab Item:

Discussion Summary:

Ask from Emerging DB:

Microsoft Response / Commitment:

Owner from Microsoft:

Owner from Emerging DB:

ETA / Follow-up Date:

Current Status:

Next Action:

GitLab Link:

--

Hi Team, I’m planning to maintain a OneNote tracker for our weekly Microsoft syncs so that MS commitments, pending asks, owners, ETAs, and follow-up items are tracked clearly.

This should help us stay prepared for each MS call and avoid losing track of action items, especially for Q2-targeted dependencies.

Please add/update any pending MS topics or GitLab links there before the call so we can follow up with clear context.

Posted By Nikhil01:21

0

Continue Reading

 

For the Microsoft-dependent items targeted for Q2, just a reminder that we should keep the GitLab updates current and use our periodic Microsoft calls to bring up the relevant pending topics.

Since Q2 has only two iterations left, let’s be clear on which items are realistically actionable, which are waiting on Microsoft, and what needs follow-up so we avoid carrying these forward unnecessarily.

Posted By Nikhil01:06

0

Continue Reading

 Epic: Q2’26 Emerging DB – Enhancements for Cosmos & Redis

RAG: Green

Status: Key items are currently awaiting release.

Update: Azure Function async pipeline change is ready to reduce wait time by enabling parallel calls. RiotX validation for Redis-to-AMR migration is also awaiting release and will support seamless migration through the pipeline.

Next Step: Track release completion and confirm post-release validation.

Posted By Nikhil00:38

0

Continue Reading

 Update: TLS policy update, ADO role-sync fix, Redis audit-to-deny policy, and low-cost AMR SKU policy are in testing. DocumentDB autoscale restriction is in progress. Redis keys-disable AINE effect for Red Zone is awaiting release.

Next Step: Complete testing/validation, track release items, and confirm closure readiness before iteration end.

Posted By Nikhil00:35

0

Continue Reading

 Hi Team,

For tomorrow’s call with Microsoft, just wanted to remind/check on the action items from the previous discussion.

As per last call, Microsoft was expected to come back on:

1. Manual switchover solution/control from user side + documentation

2. Estimated timeline to share required details

3. Microsoft distribution list / contact group for follow-ups

Not sure if these details have already been shared. If yes, let’s review and prepare any queries/inputs before the call. If not, we can follow up with Microsoft tomorrow and ask for clear next actions/timelines.

Posted By Nikhil05:42

0

Continue Reading

 Hi Team,

I have created a few GitLab items based on points discussed in recent Documentation and Product/RO sync calls.

Please review them during your internal discussions and add any required details/comments so we can get better clarity before bringing them into scrum/planning.

Also please confirm if any item needs refinement, priority, ownership, or iteration alignment.

Posted By Nikhil05:23

0

Continue Reading

 Hi Team, quick reminder on the Eng tenant access issue.

Since this has been pending for a few days and is impacting a linked iteration item, can we please align on the blocker, owner, and next action before tomorrow’s scrum call?

This will help us avoid carrying the blocker further as we are close to iteration closure.

Posted By Nikhil04:40

0

Continue Reading