I'm setting up the Logitech TAP for the first time and seem to have run into an issue. We run Exchange Hybrid and Teams only (our SfB on-prem server was decommissioned recently) - I was able to follow the instructions from the MS Docs site, and skipped the Powershell commands for SfB.
I can log in using the meeting room credentials, and I can make and receive calls - the only thing I can't see are the upcoming meetings that I created for today. Has anybody seen this issue before?
Related
I hope somebody can help me with this issue.
I recently moved my azure pipeline approval release process from slack web hook to Azure pipeline App for slack, because I found that having the approve and reject button directly in slack chat was something really nice to have to make approvals easier.
This is the process I follow:
Install Azure pipeline App in slack workspace
Create a private channel and /invite #azpipelines
I signed in /azpipelines signing
Once those steps has been completed, I started to subscribe my release pipelines selecting the stages I was interesting in. Everything worked just fine for a couple of days, I was receiving the notifications and I was able to approve and reject them without any problem, which is great, but today, out of nowhere I realised that I was receiving the emails from azpipelines that a release has been issued but no notification in channel.
The documentation about azure pipeline is really poor and I have no idea what is going wrong with the configuration.
Did this happen to anyone before and can direct me on the right path of what could be the issue behind it?
Thank you very much for any help you can provide
Sometimes, I also could encounter the similar problems.
And many times, I can fix the issue via the following ways:
Unsubscribe and re-subscribe the notifications.
Log out and then log in again.
Uninstall and re-install the Azure Pipelines App.
May be you also can try this steps to see if the issue can be resolved.
I am using Play console internal testing with fastlane upload.
Suddenly, Google started review my internal testing.
I know the internal testing is fast distribution process without review for small internal tester group.
Is there any change in policy? I can't understand this issue
I could get a response from google play console help support team.
In my case, my last release was rejected because of invalid test id/password.
So second case includes my case.
Hi there,
I'm sorry we got disconnected during our chat today - please let us know how we can help resolve your issue. If you'd prefer to contact us again via chat support, we're available Monday through Friday, 12 am to 12 am GMT.
We also offer email support 24/7. Just respond to this email and I (or one of my teammates) can pick up where we left off.
In most cases, if you upload an app bundle to an internal test track, changes will be immediately available. App updates on internal test tracks are not subject to reviews but may be subject to retroactive reviews after going live on the Play store.
There are two caveats to note regarding reviews and internal test tracks:
If your app's first release roll-out is on an internal test track, the submission must be reviewed before it can be published. Reviews can take a few hours or up to 7 days (or longer in exceptional cases), as it depends on the review time that your app is subject to.
If your previous submission has been rejected, the next submission must be reviewed before it can be published. In this case, if you upload an app bundle to an internal test track, changes will not become available until the review is complete and approved.
Regards,
Belle
Google Play Developer Support
recently my company started using Bitrix24 as an intranet portal. Our employees use google drive and calendar synchronization between their google accounts (private ones, not gsuite). Few days ago I received an email from google:
We have contacted Bitrix24 support, but they could not give us any specifics with regards to this email and pointed out to contact google. Free google plans do not really have helpdesk support and point to sites like stackoverflow for help.
We do not really know what to do in this situation, as we have very little knowledge about google developer console. One of us just used his account to set up a project and provide OAuth to sync google accounts with bitrix24.
Several months ago google started releasing security changes enacted to help ensure that users data is secure. Due to this all developers with applications running risky scopes must apply for application verification
The developer who has created this application, probably the same person who received that email must click the link and submit the application. Once your project is approved you will not have any more issues. I suggest you begin the process now as it may take sometime for you to compete the process.
EDIT #2: Looking into this issue further I have found that this feature, FEATURE ID: 26955 link is in the process of rolling out. I think this might have something to do with my issue. Any help would still be appreciated.
EDIT: I think something must have changed in how the connect to office365 button works or how grouping is done in teams. I found a strange workaround where if I create a group in Outlook and base my Microsoft teams group off that already created office 365 group, I can successfully connect to that group using my custom connector. But any time I create a team in MS teams, I don't see that team in outlook and then keep receiving the server error when trying to connect.
I created a custom connector last week for MS Teams and connected it to a few of my channels. This week I created a few new test groups and channels and the connector is no longer working. I keep receiving a 500 error from the connect url like the image below.
My old channels from last week still work fine with my sideloaded connector. Any new group and channel I create keeps running into the server error I see below.
Any help at all would be much appreciated. I have also managed to receive this error intermittently from connectors in the store.
Similar to this post from a few days ago, I am also receiving an error when I try to delete the sideloaded app: Custom Microsoft Teams Connector doesn't communicate with an external service at all
Error received from Microsoft connect url (Office 365 button)
#caits also reached out via email on this. Upon further investigation we discovered that this is caused by the fact that the connector code is calling a Graph API that is checking to see if the current user is a member of the team but when a user creates a team is created from Teams, that user is made an owner. We are changing the joinedTeams API so that it includes owners and members, which should fix this.
There was an issue when we try to configure connector for newly created team. This issue has been fixed.
Open browser
Navigate to http://www.windowsazure.com/en-us/
Select portal top right
login with my email address
Receive the below error
https://manage.windowsazure.com/Error/Login?getsupport=true&f=255&MSPPError=-2147217320
Receive the error
" We are having trouble logging you into the portal
Please contact Customer Service for assistance."
Using IE or Chrome, incognito or not, cookies cleared or not, cache cleared or not. The problem still exists. Also tried on multiple devices media centre PC, desktop running windows 7, iPhone 5, ipad 3...
Prior to November 2012 I have accessed the windows azure subscription without a problem.
I clicked the customer service link and the australian number is 13 20 58 I have contacted that number explaining that I cannot access my windows azure subscription and each time I login I receive an error. They proceed to redirect me to other support teams where I repeat my details and the problem they either redirect me again or provide a number to call.
In one case I was redirected to a number that no longer exists. Another I was told to raise a case on the windows azure portal page the same portal page that I receive an error on when logging in, when I asked for alternative options there were none.
So far I've spoke with the msdn support team, windows subscription support, online services, etc and still no resolution. In the latest call to support they have said to raise the issue on the forums so here goes.
Anyways long story short I have probably spent 3+ hours calling Microsoft support explaining the problem, waiting on hold, being redirect, repeating... still I can't access my windows azure subscription
I checked in commerce.microsoft.com and there is a windows azure subscription associated with my email address
Subscription-1
Windows Azure MSDN - Visual Studio Premium
Does anyone have any suggestions on how to resolve this issue?
Some time it's happened wait for while and retry
or just ask azure support in twitter
Editing for those who are like me and skipped reading the comments (in small font) below the OP's question. This was resolved and was due to the first reason I list below. However, it could (and has) happen in past for other reasons as well, so might as well keep this response here in case it helps someone else out.
Try logging at https://portal.azure.com/
The manage.windowsazure.com isn't even DNS resolvable to any website - I am not sure how you are getting that address (maybe its from some part of Azure IAM pipeline that hasn't been updated) and (more interestingly) how you are able to open that link - Maybe this is something available only in your region ! (but I am stretching here).
Regardless, I also tried to find other instances of similar issues and in general I see this issue is related to cases when the an account has been transitioned to Office 365.
Here an account was moved and resulted in creation of two accounts with different passwords - solution here was to set the Office 365 account (new account) as a co-admin on the old account that was used to setup the Azure account.
Here the account was not provisioned correctly in Azure AD Store and had to be removed and re-created using DirSync
Here, the problem seems to be related to (the new) Account Provisioning in Azure AD.
In general, it seems this is a problem that might be harder to explain to level 1 support. You might have better mileage speaking to your organizations IT admin and have them check for any inconsistencies that might be similar to those stated above.
Try forcing the directory in the URL like so
https://portal.azure.com/#domain.name
For example in case of MS AAD domain
https://portal.azure.com/#mycompany.onmicrosoft.com
In case of custom domain
https://portal.azure.com/#mycompany.com
Sometimes there is some odd behaviour with redirect loops or when you no longer have access to the tenant but you have selected 'last visited' in the Startup directory.
Glad to hear this was resolved by support. Since this was posted, we made a number of updates to the login process and types of accounts (incl. the addition of MFA). At TechEd we announced a new portal (video # http://channel9.msdn.com/Blogs/Windows-Azure/Azure-Preview-portal) if you want to see what is coming.