Since Jörgen said he expected the statement “today or tomorrow,” and the message was sent yesterday afternoon, I would wait until later today. Dhirendra has already asked the key follow-up question, so another message from you this morning may look like duplicate chasing.

If nothing arrives by late afternoon, send:

Hi Jörgen, just following up on the formal communication you mentioned yesterday. Could you please share it with Dhirendra and me once available? It would also be helpful if it includes the expected plan and timeline for resolving the capacity constraint. Thanks.

Posted By Nikhil06:28

0

Continue Reading

 

Title

Fix duplicate user entries in RoleSync user list

Description

The updated RoleSync steps currently populate the user list using the Object ID instead of the corresponding user name. As a result, the user name and Object ID comparison does not match correctly, which can lead to duplicate or misleading entries in the generated user list.

There is currently no functional impact, but the output may be confusing for users and could also result in incorrect interpretation at the code level.

Proposed Fix

• Use the Object ID as the unique identifier when comparing users.
• Resolve and map each Object ID to the corresponding user name for display.
• Ensure duplicate users are not added to the RoleSync user list.

Acceptance Criteria

• Users are compared using their Object IDs.
• Each Object ID is displayed with the correct user name.
• No duplicate user entries are generated.
• Existing RoleSync functionality remains unaffected.
• Relevant test cases are added or updated.

Posted By Nikhil02:09

0

Continue Reading

 Suggested three-session sequence

Secure Cosmos DB Onboarding: RBAC, Group-Based Access and CMK

Cosmos DB Resilience: Multi-Region, Failover, Backup and Restore

Cosmos DB Cost and Performance Optimisation: RU, Indexing and Guardrails

Posted By Nikhil18:43

0

Continue Reading

 

1. Secure Cosmos DB Onboarding: RBAC, Managed Identity and CMK

External — Microsoft Product Content	Internal — Bank Process and Governance
Cosmos DB control-plane and data-plane RBAC	Internal access-request and approval process
Built-in and custom roles	Human-user and technical-user onboarding
Microsoft Entra ID and managed identities	MIM/Group ID creation and assignment
Group-based access management	Role Sync and future Group ID access model
Customer-managed keys and Key Vault integration	CMK ownership, Key Vault access and audit evidence
RBAC troubleshooting and common errors	Support ownership and escalation process

2. Cosmos DB Resilience, Backup and Disaster Recovery

External — Microsoft Product Content	Internal — Bank Process and Governance
Availability zones and multi-region deployment	BCM initiation and approval process
Single-write and multi-write region design	Internal RPO and RTO expectations
Automatic and manual failover options	Failover ownership and communication process
Continuous backup and point-in-time restore	Restore-request and validation process
Failure scenarios and recovery options	Change, incident and escalation requirements
Microsoft support process for backend failover	BCM evidence and exercise documentation

3. Cosmos DB Cost and RU Optimisation

External — Microsoft Product Content	Internal — Bank Process and Governance
Request Unit calculation and consumption	Internal cost ownership and reporting
Manual versus autoscale throughput	Lower-environment throughput standards
Database-level versus container-level throughput	Approval process for high-cost configurations
Query, partition-key and indexing impact on RUs	Audit-to-Deny policy lifecycle
TTL and storage optimisation	Cost exception and expiry process
Monitoring and identifying high-RU operations	Cost tracker and periodic review process

4. Cosmos DB Performance Troubleshooting for Application Teams

External — Microsoft Product Content	Internal — Bank Process and Governance
Troubleshooting latency and throttling	First-level checks before escalation
HTTP 429 errors and SDK retry behaviour	Application-team versus SRE ownership
Hot-partition identification	Required information in support tickets
Query and indexing optimisation	Internal incident and escalation process
Regional preference and SDK configuration	Log, metric and evidence requirements
Cosmos DB monitoring and diagnostic tools	GitLab tracking and follow-up ownership

5. Policy-Compliant Cosmos DB Deployment

External — Microsoft Product Content	Internal — Bank Process and Governance
Secure Cosmos DB deployment patterns	Internal Control Plane and pipeline workflow
Backup, networking, CMK and RBAC configuration	Mandatory policy metadata and category values
Private endpoint configuration	CI validation and release requirements
Azure Policy effects: Audit, Deny, DINE and AINE	Internal policy review and approval lifecycle
ARM, Bicep and Terraform considerations	Policy tracker, evidence and ownership
Recommended compliance controls	Exception and remediation process

6. Cosmos DB Migration and Adoption

External — Microsoft Product Content	Internal — Bank Process and Governance
Account and container migration approaches	Application onboarding and eligibility assessment
Container Copy and supported migration tools	Internal approval for Preview features
Source-to-target connectivity requirements	Migration Factory engagement process
Data validation and reconciliation	Naming and policy-compliance checks
Migration performance and RU planning	Production-readiness and change approval
Rollback and post-migration validation	Ownership, support and decommissioning process

Posted By Nikhil18:41

0

Continue Reading

 etcdctl --endpoints=http://127.0.0.1:2379 \

  endpoint status --write-out=json |

python3 -c '

import json

import sys

data = json.load(sys.stdin)

print("{:<30} {:>12} {:>12} {:>16} {:>12}".format(

    "ENDPOINT", "DB_MiB", "IN_USE_MiB", "FRAGMENTED_MiB", "FRAG_%"

))

for item in data:

    status = item["Status"]

    total = status.get("dbSize", 0)

    used = status.get("dbSizeInUse", 0)

    fragmented = max(total - used, 0)

    percentage = fragmented * 100 / total if total else 0

    print("{:<30} {:>12.2f} {:>12.2f} {:>16.2f} {:>11.2f}%".format(

        item["Endpoint"],

        total / 1048576,

        used / 1048576,

        fragmented / 1048576,

        percentage

    ))

'

Posted By Nikhil21:54

0

Continue Reading

 etcdctl endpoint status --cluster -w json |

jq '.[] | {

  endpoint: .Endpoint,

  dbSize: .Status.dbSize,

  dbSizeInUse: .Status.dbSizeInUse,

  reclaimableBytes: (.Status.dbSize - .Status.dbSizeInUse)

}'

Posted By Nikhil21:52

0

Continue Reading

 export ETCDCTL_API=3

etcdctl \

  --endpoints="https://etcd1:2379,https://etcd2:2379,https://etcd3:2379" \

  --cacert=/path/to/ca.crt \

  --cert=/path/to/client.crt \

  --key=/path/to/client.key \

  endpoint status --write-out=json |

jq -r '

  def mib: . / 1048576;

  ["ENDPOINT", "DB_MiB", "IN_USE_MiB", "FRAGMENTED_MiB", "FRAGMENTED_%"],

  (

    .[] |

    .Status.dbSize as $total |

    .Status.dbSizeInUse as $used |

    [

      .Endpoint,

      (($total | mib) * 100 | round / 100),

      (($used | mib) * 100 | round / 100),

      ((($total - $used) | mib) * 100 | round / 100),

      ((($total - $used) * 10000 / $total) | round / 100)

    ]

  ) |

  @tsv

' | column -t

Posted By Nikhil21:49

0

Continue Reading