User Profile
vbakshi123
Copper Contributor
Joined Apr 24, 2021
User Widgets
Recent Discussions
Re: Entra Private Access - Private DNS
I managed to resolve it in some way. Even though you are correct, it won't resolve the private DNS name of any of the devices in the on-premise network We had a Entra Global Secure Access app that had port 3389 access to the entire domain, i.e. *.yourdomain.com I suspected that after enabling private DNS, somehow the namespace was conflicting between the Quick Access app and the entra global secure app since the private dns name and the domain name are obviously the same. Even though they are meant to be communicating on different ports. So, I removed that entry from the entra global app and then enabled private dns, then our access to the other private apps were unaffected. For password change, we opened the relevant ports on the same quick access app which allows private dns. Creating a separate enterprise app for DC communications whilst having private DNS enabled on the quick access app didn't seem to work that well. The only issue we have is looking up DNS names , but only getting magic IP's instead of the private IP address.1.5KViews0likes0CommentsEntra Private Access - Private DNS
Hello Everyone We are using the trial period of Entra Private access and Entra Internet Access using Global Secure Access client. We recently got the Private DNS feature within Quick Access under Global Secure Access. The moment, we added our on-premise domain suffix to create a line of sight to the DC's, access to other private apps, some of which are actually cloud web apps stopped working. The cloud app web portals won't open, RDP to servers were not working. Intermittently, we could open the portal or RDP to the server, but everything had just died down. After leaving it for more than 8 hours, the issues were still not going away, so we removed the quick access app and disabled private DNS, issue was resolved after that. Any ideas why ? Also, is there a way we could allow our on-premise user accounts to change their passwords when it expires or get those password expired notifications as we did when we used Cisco VPN. We have Azure hybrid-joined machines with GSA running in them, but users don't get password expiry notifications, nor can they change the password on the local Laptop as it can't talk to the DC's. We created an app with Kerberos port 88, LDAP 389 and 464, still password change doesn't work. Users are logging in to the Laptops with cached passwords.2.6KViews0likes4CommentsRe: Sensitivity label works in Outlooks web app but not desktop app
We were able to fix it by deleting the mip folder in Outlook so it pulls the new template down. That being said, it still affects new users and it is not feasible to continually delete this folder for each user. The mip folder is: %LOCALAPPDATA%\Microsoft\Outlook\MIPSDK\mip This is occurring for Exchange Online and seems to only affect the newer versions of Office (i.e. Semi Annual does not have this issue).1.4KViews0likes0CommentsSensitivity label works in Outlooks web app but not desktop app
We are currently using M365 Business Premium licence and hence are using Azure Information Protection Premium Plan 1. We created an 'Internal' sensitivity label on compliance.microsoft.com, with "assign permissions now" configuration granting co-author access to all users and groups within the organisation . The label is working in the user's Outlook web app. However, when drafting a new email in Outlook desktop app, the option to select the label is there, but when I click on the label itself it reverts back to "no label". All the users to which label policy is scoped can see the Label. but can't apply it. Some insights: 1. If I create a label with "Let users assign permission" configuration and then select the "Encrypt-Only" or "Do-Not-Forward" options. Then users can see that label and apply it in the Outlook desktop app and web. 2. If I create labels with "Assign Permission now" configuration, scope it to both file and email, grant co-author access to 'Authenticated Users', or 'all users and groups within the organisation', then users can select the label in Word/Excel etc, but not Outlook Desktop app. They can assign the same label in Outlook Web though. We are on the latest - Microsoft® Outlook® for Microsoft 365 MSO (Version 2403 Build 16.0.17425.20176) 64-bit. We use built-in labels by Office apps and never used AIP unified labelling client or the classic client.SolvedAVD Standard Windows client has horrible audio quality on Azure Virtual Desktops. Works great with M
A bit of a long story, so please be patient 🙂 Our environment has got RDP shortpath enabled and clients make successful UDP connections to the Windows 11 Enterprise 21H2 AVD's. RTT is very low as well within 20 ms. We don't plan to use Windows 10 OS, hence QOS enablement is not done for the AVD's When the agent connects to the AVD using standard Windows client available at https://learn.microsoft.com/en-us/azure/virtual-desktop/user-documentation/connect-windows-7-10 and takes calls on Avaya One-X Communicator App version 6.2.7.03-SP7 , the call is jittery and it crackles as well. The agent can hear the customer fine, but it is mainly the customer which faces issue with the jitter. The QOS call quality shows 'good' on the Avaya app. We haven't done deep level troubleshooting and log collection on the Avaya app, since it's working fine in other environments as you will find below (so not an internal infrastructure issue which involves the Avaya server or it's DB) When the same agents connects to the same AVD using the MS Store RDP client available at https://learn.microsoft.com/en-us/azure/virtual-desktop/user-documentation/connect-web, they don't face any audio problems. The customer and the agent can hear each other and converse much better with minimum jitter and delay in audio. It is at an acceptable. Additionally, we have the same set of users who don't face any problem on AWS Workspace as well. The difference in AWS Workspace and AVD is AWS uses Teradici audio drivers and the OS is Windows 2019 with desktop experience. We pay per-user licence fee to AWS for potentially the Teradici offering which allows us to connect to the AWS VDI's using PCOIP protocol. instead of RDP/UDP that we have on Azure Virtual Desktops I am at a loss right now to think of what else may be causing these jittery and poor call quality issues, and why we don't face it on the Microsoft store RDP client. The only reason we can't use the Microsoft store RDP client because it doesn't support dual monitor. I have been looking at the Teradici offering for Azure Virtual Desktops (thinking that may be PCOIP connectivity is the solution using Teradici audio drivers) and had the below questions : 1. Without moving to Teradici, is there any other piece that I am missing which may resolve the issue without moving the architecture to PCOIP which means involving Teradici ? 2. Need to understand the pricing, is it 86.427 £ per user per month with a minimum of 5 users to subscribe ? Does the one-time payment mean we pay only once 86.427£ for each user and the CAS licence will be valid for a year, post which it gets renewed with another 86.427£ 3. After going through the documentation, it seems that Teradici has a PCOIP client for Ubuntu OS to connect to an existing Azure Virtual Desktop. Is this correct ? Our users are all windows users. How will they connect using PCOIP to the existing Azure Virtual Desktop hosted in Azure ?3.5KViews0likes0Comments
Recent Blog Articles
No content to show