User Profile
MarkMiddlemist_Mercato
Copper Contributor
Joined Jul 18, 2019
User Widgets
Recent Discussions
Securing app services across multiple AAD tenants
Hi All I'm beating my head against a wall so wanted to see if anyone can please help me out, or at least point me in the correct direction. We have a large Azure infrastructure across multiple AAD tenants, with a number of app services that we're trying to secure at the network level using app service restrictions so access is only allowed from clients within our infrastructure (across the 2 tenants), or using controlled access via our APIM and Front Door edges. The clients are a mix of other app services, VMs, VM scale sets (service fabric), and APIM access routes. All these now have Subnets attached for outbound routing. For securing within the same tenant everything works beautifully, using subnet access rules to grant access to the service endpoints from the client subnets. Where we are having problems is the cross-tenant allow rules. All the subnets have NATs attached with IPv4 public IPs, which I had assumed would mean that we'd be able to use the public IP to grant the access on restrictions in the other tenant. However what we've realised when we tested was that the presence of the Microsoft.Web service endpoint means that the NAT is being bypassed, and the IP presented to the target app service is not the IPv4 address we were expecting but an IPv6 address that is apparently used by the service endpoint, and I'm presuming not reliably static even if we can figure it out. I presume we're not the first people ever to try and achieve the goal of cross-tenant app restrictions so thought I would ask how this is best done? The one suggest I was given was to remove the service endpoints but that of course stops us being able to use subnet app restriction rules, and I failed to get anything to work with any of the IPs associated clients. Thanks in advance for any help you can offer Mark MiddlemistRe: Teams app crashes when sharing the screen
I'll be honest the only thing that actually solved this for me was a complete clean reinstall of Windows from scratch. No hardware has changed, but for some reason it worked on the clean setup. Sorry it's not better news, but hope this does help80KViews0likes3CommentsRe: Teams app crashes when sharing the screen
Wrangler1730 Thanks for the comment. I'm not sure what was going on. I actually had cause to do a clean install of windows a while ago, and it's been fine since then. Hope anyone else experiencing the issue can get a proper resolution though98KViews0likes1CommentTeams app crashes when sharing the screen
Hi All I'm currently running the Teams app 1.3.00.13565 (64 bit) running on Windows build 19042.388 (Version 20H2) and when I am on a call and share a screen (tested with entire screen or specific app) the teams app completely crashes. I've checked in the event log and am consistently seeing the following entry when the crash happens: ==== Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Microsoft Teams because of this error. Program: Microsoft Teams File: The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: 00000000 Disk type: 0 ==== There is actually 2 Application errors, and a Windows Error Reporting entry that come in unison. If anyone could help it would be much appreciated, as this is stopping me from being able to fully work at the moment Thanks in advance MarkSolved124KViews2likes28CommentsRe: An internal error occurred / can't connect anymore
Roop_Kiran_ChevuriGlad to hear there is a fix underway. Can you provide us at least a rough ETA please. We are currently investigating moving some of our systems to WVD but right now our investigations and POCs have had to go on hold because of the broken resource templates and now this. Can you also please comment as to when this service will be covered under full support and SLA if clients such as ourselves are looking to go to market, Thanks in advance Mark5.4KViews0likes0Comments
Recent Blog Articles
No content to show