For storage and VM, I can check the current quota usage by following powershell command:
Get-AzureRmStorageUsage
Get-AzureRmVMUsage
Is there similar thing for Azure Search? Either via powershell or Portal is ok.
In addition to monitor usage on portal, you could also get it via Service Statistics.
The Service Statistics request is constructed using HTTP GET and returns from Azure Search the current usage and limits of the following properties.
GET https://[service name].search.windows.net/servicestats?api-version=[api-version]
Content-Type: application/json
api-key: [admin key]
how many S2 or S3 services I can created on a give region?
You can create multiple services within a subscription. Each one can be provisioned at a specific tier. You're limited only by the number of services allowed at each tier. For example, you could create up to 12 services at the Basic tier and another 12 services at the S1 tier within the same subscription. Please refer to this article.
There is an easy way to check your quota usage for an Azure search service, via the portal:
If you open up the overview tab for you search service, you'll be presented with something like this: (image from a search service that I've created)
This shows the quota of resources for your search service and how much of the quota has been used up.
https://learn.microsoft.com/en-us/azure/search/search-limits-quotas-capacity
By using above url if you know what is your service plan then you can see the limits
Related
I'm looking to understand the age of stores in Azure maps.
Does Azure provide a way to query when a particular store opened?
Azure Maps doesn't have that information in their services. To be honest, I haven't seen that in any service from anyone.
I have not started any script yet but wanted to check first If this can be achieved to configure Azure AD Non gallery enterprise app using PowerShell that let me enter metadata such as entity id, reply URL, sign-on URL and attributes information.
I need a suggestion to start on this If you could shed some lights?
For powershell, this is not currently possible.
In May, Microsoft added the ServicePrincipals endpoint to 1.0 graph api for (enterprise applications). So using graph api, you may be able to accomplish it. I know until very recently this was still not possible, however checking today the updateserviceprincipal endpoint seem to have the replyurls attributes and loginurl and the serviceprincipalnames (entityid?)
So there is a good chance you could get it to work using graph api. but you may have to use the beta graph endpoint.
I would use this endpoint to create the application: https://learn.microsoft.com/en-us/graph/api/applicationtemplate-instantiate?view=graph-rest-beta&tabs=http I believe the custom basic saml app template id is : 8adf8e6e-67b2-4cf2-a259-e3dc5476c621
after creating it. you would need to find the service principal objectid and set the signinmode to saml:
Here are all the necessary calls and example. https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/application-saml-sso-configure-api#step-2-configure-single-sign-on
Using the Microsoft Graph API I need to be able to update the attribute proxyAddresses as part of our provisioning process to enable self-service password management for our end users.
I see that this attribute is read-only from the Graph API but as of 8 months ago MS was entertaining the possibility of making it RW. Does anyone have any color on this, has anyone found a workaround to this issue via API?
This isn't supported in either v1.0 or Beta at the moment but this is an open OverVoice request for this feature: Ability to update the user's email aliases (proxyAddresses attribute).
Also if you are working with bigger customers - usually you want to sync their identities from local Active Directory using AD Connect tool. In that case you should implement things and change proxyaddresses attribute in local AD, because it is the "identity authority" (means that you can't change it on cloud side and it must be done in on-prem AD).
So it could be workaround for problem you are trying to solve.
Also if it is cloud only (not synced) identity - you can use PowerShell to modify proxyaddresses attribute on users.
Here is documentation on how to do that - https://technet.microsoft.com/en-us/library/bb123794(v=exchg.160).aspx
I am building an iPhone app that stores user logon credentials in an AWS DynamoDB. In another DynamoDB I am storing locations of files (stored in S3) for that user. What I don't understand is how to make this secure. If I use a Token Vending Machine that gives that application an ID with access to the user DynamoDB, isn't it possible that any user could access the entire DB and just add or delete any information that they desire? They would also be able to access the entire S3 bucket using this setup. Any recommendations on how I could set this up securely and properly?
I am new to user DB management, and any links to helpful resources would be much appreciated.
Regarding S3 and permissions, you may find the answer on the following question useful:
Temporary Credentials Using AWS IAM
IAM permissions are more finegrained than you think. You can allow/disallow specific API calls, so for example you might only allow read operations. You can also allow access to a specific resource only. On S3 this means that you can limit access to a specific file or folder , but dynamodb policies can only be set at the table level.
Personally I wouldn't allow users direct access to dynamodb - I'd have a webservice mediating access to that, although users being able to upload directly to s3 or download straight from s3 is a good thing (Your web service can in general give out pre signed urls for that though)
Does anyone know what the difference is between the two web service endpoints ReportService2005.asmx and ReportExecution2005.asmx in SQL Server Reporting Services? is there an article that I can go through? Thanks.
The ReportExecution2005 endpoint allows developers to programmatically process and render reports in a report server. The WSDL for this endpoint is accessed through ReportExecution2005.asmx?wsdl.
The ReportService2005 Web service (reportservice2005.asmx) allows developers to programmatically manage objects in a report server.
As Mitch says, ReportExecution2005 is for executing reports, handling drilldown, rendering, etc. and ReportService2005 is used for creating things (data sources, subscriptions, even reports), as well as updating, deleting, querying, etc.
Two handy references are the MSDN method listings for ReportExecutionService (ReportExecution2005 web service endpoint) and ReportingService2005 (ReportService2005 web service endpoint).
Don't confuse these with the ReportService2006 endpoint, which is used if you have SSRS configured for Sharepoint integrated mode.
Hope that helps!
ReportService2005
Enables you to manage a report server and its contents including server settings, security, reports, subscriptions, and data sources.
Can be accessed by: http://servername:port/ReportServer/ReportService2005.asmx?wsdl
ReportExecution2005
Enables report execution
Can be accessed by: http://servername:port/ReportServer/ReportExecution2005.asmx?wsdl