Hi Marcin,
Thanks for raising this. We would like to review internally whether AACM requests would still be required if the AKV URI remains unchanged, and accordingly confirm the need for SAML enablement.
Could you also clarify which specific Microsoft access restriction you are referring to? We expect to revert with a confirmed response by tomorrow.
Thanks,
Nikhil
Hi Marcin,
Yes, your understanding is correct. Although the Key Vault migration is currently on hold and the AKV URI remains unchanged, the AACM requests will still be required due to the access restrictions being introduced by Microsoft.
Therefore, we should proceed with the SAMI enablement as planned.
Best regards,
Nikhil
Subject: LGTM Deployment Review – Open Items and Next Steps
Hi all,
I am setting up a short discussion to review the remaining LGTM deployment items and align on priorities, ownership, and next steps.
Agenda:
db_detect behaviour, and the follow-up with LaszloI have kept the call brief and focused on decisions and actionable next steps.
Sharing this for awareness:
During installation activities over the weekend, I observed an issue affecting the PISA components. I initially suspected possible infrastructure maintenance; however, the issue continued into Monday.
An incident was raised with the PISA team, and Norbert investigated and drove it through to resolution yesterday evening. The issue was identified as a DNS resolution problem at the GSLB layer and has now been resolved.
Thanks to Norbert for the prompt support.
Incident reference: INC2008696536
Subject: Guidance on missing orapki utility / symbolic links
Hi Laszlo,
While working on the Alloy certificate installation as part of the LGTM onboarding, I noticed that the orapki utility is unavailable on several hosts. In some cases, the utility itself appears to be missing, while on others the symbolic link to the expected directory is either missing or no longer valid.
Since you are familiar with these environments, could you please advise whether there is a known reason for this? I was also wondering whether there have been any recent changes that may have affected the installation or symbolic links.
It would be helpful to understand:
orapki, where requiredorapki is expected for certain host types or configurations and should not be treated as a missing componentYour guidance will help us determine the correct approach before proceeding with remediation across the affected hosts.
Thanks in advance for your support.
Regards,
Nikhil
Subject: Emerging DB Cost Optimization – Q3 Follow-up
Hi Team,
Thank you for your valuable inputs during our recent discussion. We made good progress in identifying practical cost optimization opportunities and agreeing on the key action items.
I am setting up this follow-up call to review progress, discuss the available cost analysis, and align on the next steps.
Agenda:
Looking forward to your continued inputs and discussion.
Please suggest an alternative time if this slot is not suitable.
Hi Team, thanks for joining.
This is our second catch-up on cost optimisation for Emerging DB. In the previous discussion, we reviewed the potential benefit of shutdown and also compared shutdown versus pause, but based on the assessment, there did not appear to be a meaningful cost benefit.
We also discussed reservations, and Dhirendra had shared some initial information on that area.
For today, I would like us to continue from there, review any further inputs on reservations, and explore additional cost-optimisation opportunities that may be practical for our products.
We can assess each idea based on expected benefit, feasibility, dependencies, and any impact on users or operations.
Azure App Service authentication: Completed the impact assessment for disabling SCM basic/local authentication. Deployments relying on the legacy authentication method were identified to ensure application deployment continues after the new security policy is enforced.
AMR geo-replica automation: Completed the DevOps API script for linking and unlinking AMR geo-replicas, providing a controlled and repeatable process and reducing dependency on manual activities.
Sweden region readiness: Readiness assessment is in progress for Sweden Central and Sweden South. Existing operational dependencies, including RoleSync and ACS processes, are being validated before enabling the new regions.
HA controls for lower environments: Audit policy implementation is in progress across AMR, Azure Cache for Redis, Cosmos DB and DocumentDB to identify unnecessary HA configurations in Dev and Test environments.
Redis SKU optimisation: Automated SKU comparison tracking is in progress to verify whether lower-environment Redis instances have moved to the approved standard SKUs.
AMR HA enforcement: Policy changes are awaiting release to move AMR HA restrictions from Audit to Deny in BA and BARZ for Dev, Test and UAT environments.
AMR SKU enforcement: Policy changes are awaiting release to restrict lower environments to approved AMR SKUs and prevent provisioning of unnecessarily expensive configurations.
MIM group role assignment: Policy implementation is in progress to automate role assignment for Cosmos DB NoSQL API resources, supporting consistent least-privilege access and reducing manual RBAC activities.
Cosmos DB zone-redundancy control: The policy for identifying non-zone-redundant Cosmos DB deployments is currently in testing under Audit mode in BARZ, ahead of future enforcement.
Cosmos DB backup compliance: Pipeline changes are awaiting release to configure seven-day continuous backup for lower-environment Cosmos DB accounts before the related backup policy moves from Audit to Deny.
Cosmos DB tagging: Completed the policy update to include MongoClusters in the Add-TagOnCOS rule, enabling the required postBuildConfig and WaitingForConfig tags on newly created resources.
AMR automatic-update compliance: Policy changes are awaiting release to move the AMR automatic-update control from Audit to Deny and prevent non-compliant configurations.
Redis provisioning control: Completed the change of the Deny-Redis-Create policy from Deny to Audit, unblocking Azure Cache for Redis provisioning while retaining compliance visibility.
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
